Solved Intermittent Connection time out error.
-
I have installed latest FOG imaging server on both Virtual BOX and standalone server, however I am running into issues when trying to PXE boot client machines.
It sometimes boots to the PXE menu and everything is fine but then when I try to run it again on same machine I get a connection time out error. I am using DHCP and DNS from the FOG service.
I have tried different kernels and the same thing happens.
-
@steharv Do you get the exactly same timeout issue or do you see it failing at various stages? Please take a picture of the timeout and post here. This way we can probably help.
-
-
@steharv Its the same error, however its intermittent and does not happen everytime, sometimes it boots straight up to the FOG menu.
-
iPXE is before kernels even come into the picture. This means the issue is somewhere between the NIC and iPXE attempting to get information.
As far as I can tell, the information it’s looking at to get its boot information (the 192.168.1.1/default.ipxe part) is inaccessible.
So you’re sure your FOG Server’s IP address is sitting at 192.168.1.1? Is there potential that something else is also handing out boot file information?
-
@Tom-Elliott Hi Tom, Thanks for the reply back. My router IP address ranges is from 192.168.100 to 192.168.1.250 -
I have set Ubuntu to fixed IP address of 192.168.1.249 which is set up as the FOG IP address, DNS and DHCP server is set to 192.168.1.1
-
@steharv Then I would highly recommend you update the IP address in
/opt/fog/.fogsettingsto match that of your FOG IP Address.Right now it’s looking at your router for the file, and it should be looking at your FOG Server for the default.ipxe file.
-
Attached is my default ISP router, just wondered if anything here is interferring?
-
@steharv Once you update the IP Address in the fogsettings file, rerun the installer. I’m also going to guess that you may need to update your storage node information.
On a secondary note, is your FOG Server providing DHCP as well as your main Router?
-
@Tom-Elliott Router is just set to default DHCP setting which is on and when installing FOG I answered yes to use FOG as DHCP server. No storage nodes, I can just reinstall FOG as can go back to a preinstall snapshot on VB.
-
@Tom-Elliott Hi Tom, I reinstalled FOG from scratch, I set the FOG server IP to 192.168.1.248 and then DHCP and DNS server the same IP but it still tries to look for 192.168.1.1 when it boots?
-
@steharv Then the problem is you have two DHCP servers on your network. This is why you’re getting access to FOG iPXE menu intermittently. Both DHCP servers are on the same network, and BOTH are issuing IP’s in the same subnet. If FOG hands out faster than the router, you’ll be able to get to FOG iPXE Menu, if not you’ll get an error.
I’d highly recommend looking into manually updating the information.
-
@steharv In your Router you should have a method to set options for Boot IP and Boot file. It’s here I would recommend updating things. In MS DHCP the options are 66/67 (66 being the FOG Server’s IP/67 being the bootfile - ipxe.pxe, undionly.kpxe, etc…)
-
@Tom-Elliott So editing the fogsettings file and rerun the installer? Can I edit the file via FTP?
-
@Tom-Elliott I cannot see any settings in my router for that?
-
-
@Tom-Elliott Would I be better off just installing DNSMasq?
-
@steharv said in Intermittent Connection time out error.:
Would I be better off just installing DNSMasq?
You probably would. Follow George’s post here (full config file) and check your dnsmasq version: https://forums.fogproject.org/topic/12133/fog-on-existing-dhcp-server/3
-
@Sebastian-Roth Thank you
-
@Sebastian-Roth I have tried restart dnsmasq but get the following error" Job for dnsmasq. service failed because the control process exited with errror code. See "systemctl status dnsmasq.service and “journalctl - xe” for details.
