ipxe.org/4c116035 timed out

[Tom Elliott]

Then something is not configured properly. Maybe your FOG server is set to look for hostname?

[A Former User]

Where can we choose that ? The strange thing is that if the server is reboot it work then same problem little after, and i haven’t changed the configuration since 4 month (the problem just occur recently)
For my information why is it trying to reach ipxe.org it need internet to work ?
Thanks

[Wayne Workman]

Can you run the troubleshooting script found here: https://forums.fogproject.org/topic/4581/let-s-make-scripts

And see if it points anything out?

I’m not sure if it’ll help but it’s a shot in the dark, you know?

[A Former User]

Hi, i will try tomorrow and tell you the result, thanks

[ch3i]

@alpilles.info said:

For my information why is it trying to reach ipxe.org it need internet to work ?

Hi,

Don’t need to have Internet on the server, it’s just the url to the error code.

Regards,
Ch3i.

[A Former User]

Hi, ok thanks.
I have run the scripts but i got some error line 19 entire number expected
nfs: unrecognized service
iptables: unrecognized service
Usage FOGMulticastManager {start|stop|restart}
FOGSnapinReplicator: unrecognized service
Usage FOGImageReplicator {start|stop|restart}
Usage FOGScheduler {start|stop|restart}
sed: -e expression n°1, caractère 4: command `s’ not finished

(i have translate some line because it was in french), else everything seem fine in the log file.

[ch3i]

@alpilles.info said:

Hi, ok thanks.
I have run the scripts but i got some error line 19 entire number expected
nfs: unrecognized service
iptables: unrecognized service
Usage FOGMulticastManager {start|stop|restart}
FOGSnapinReplicator: unrecognized service
Usage FOGImageReplicator {start|stop|restart}
Usage FOGScheduler {start|stop|restart}
sed: -e expression n°1, caractère 4: command `s’ not finished

(i have translate some line because it was in french), else everything seem fine in the log file.

For NFS the command is (I think) :

service nfs-common status

For FOG services, in 1.2 there is no “status” added in these scripts.

[A Former User]

yes nfs-common status doesn’t exist, for now i have add my dns server in FOG_PXE_IMAGE_DNSADDRESS andi turn off FOG_USE_SLOOPY_NAME_LOOKUP
it seem to work better i will do some other test.

[Tom Elliott]

I believe the correct command is:
sudo service nfs-kernel-server status

If on Ubuntu 15? or Debian 8 it would be:
sudo systemctl status nfs-kernel-server.service

[A Former User]

@Tom-Elliott said:

service nfs-kernel-server status

yes it’s that :
service nfs-kernel-server status
nfsd running

ubuntu 14

so the problem is elsewhere, but like i said right now it work with the FOG_PXE_IMAGE_DNSADDRESS but it used to work without it, it’s very strange
Thanks for your help.

[A Former User]

Hi, i have notice with many test that the problem seem to be random, i put a task download or upload computer half time this work wells half time i have this error (and i reboot and do it again no error) like i said totally random i don’t have any idea why but that’s annoying, is someones has ideas.
Thanks

[ch3i]

@alpilles.info said:

Hi, i have notice with many test that the problem seem to be random, i put a task download or upload computer half time this work wells half time i have this error (and i reboot and do it again no error) like i said totally random i don’t have any idea why but that’s annoying, is someones has ideas.
Thanks

Hi,

How your network is configured ? (ACL, VLAN, …)

[A Former User]

I have acl/vlan (but they have not changed recently only my fog version have changed) and the fog server is on the same vlan as the computers

[the_duke]

This post is deleted!

[ch3i]

This post is deleted!