no such device or address

Sebastian Roth

@sapeurorca On first sight the output looks pretty good to me! I am really puzzled from the 5... No such file or directory... message in your last picture. Have you tried several times? Do you always get the exact same error messages?

sapeurorca

yes i tried several times with same error messages.

george1421

@sapeurorca Well I see your error in the boot.php page.

For both the bzImage and the init.xz files, they are missing the path to the files.

i.e. http://192.168.10.24/fog/service/ipxe/bzImage32

Tom Elliott

I was chatting with @sapeurorca yesterday and had him run a few tests in light of the schema update issues. These tests had added duplicate keys into the globalSettings table.

The problem that was being seen is from more data being returned than what was actually being requested (because of the duplicate entries.)

You can actually see the problem in the browser code too. In the browser we tend to not have users sending an arch value. This means any browser url will send out the 32 bit files.

If you look in the returned output from earlier, however, you will see it’s setting the kernel to bzImage (when it should be bzImage32).

Tom Elliott

I should add, this is specific to the ipxe error that was being seen. Everything else, however still holds true.

If others are hitting similar snags there’s a way to fix. It’s two SQL statements needed and some information gathering first.

In mysql you would run (while on the fog database):

SELECT settingKey,count(*) c, MAX(settingID) FROM globalSettings GROUP BY settingKey HAVING c > 1;

This might output something like:

±-----------------------±–±---------------+
| settingKey | c | max(settingID) |
±-----------------------±–±---------------+
| FOG_GRACE_TIMEOUT | 2 | 191 |
| FOG_LOGIN_INFO_DISPLAY | 2 | 192 |
| FOG_PXE_MENU_TIMEOUT | 2 | 73 |
| FOG_USED_TASKS | 2 | 190 |
±-----------------------±–±---------------+

The last column (the max(settingID) field) is what we’re interested in.
With this info you can then run:

DELETE FROM globalSettings WHERE settingID IN (191, 192, 73, 190);

Tom Elliott

Remoted in and added:
search <domain name> to the /etc/resolv.conf file.

I don’t know if this will be automatically added or not, but hostnames by themselves are now pingable from the fog server.

sapeurorca

Now :

Ping its OK
Cloning its OK
Hostname changer and registration domain - Failed. But i think is a client, I will do several tests and I will post a new topic if I have a problem.

Very thank for this help.

osandag

Hi, Was this issue resolved?
I have a same or similar issue where the host status is green for about the first ten minutes till i register the host image it, but after a while fog says ‘no such device or address’

Given the age of the issue, has it been fixed or I have to follow the SQL edit procedure?

kboutelle

@osandag said in no such device or address:

Hi, Was this issue resolved?
I have a same or similar issue where the host status is green for about the first ten minutes till i register the host image it, but after a while fog says ‘no such device or address’

Given the age of the issue, has it been fixed or I have to follow the SQL edit procedure?

I just had the same issue that you are describing. The way I fixed it was to ensure that my interfaces file (Ubuntu server) was configured correctly. In my case, I was using search [domain] instead of dns-search [domain]. Once I fixed that, all was well.

no such device or address

183

11.6k

17.1k

154.6k