Host seems reachable by fog, but is not reaching PXE fog menu
-
@thebrennan47 Well now after looking at that picture my neck hurts…
There is a whole bunch of craziness in that picture.
What is host 192.168.1.1?
What is host 10.0.80.49?
And the last issue is the line with http///fog/service/ipxe in it. That should have an ip addressI see it tftp booting from 192.168.1.1 then connecting to 10.0.80.49 (which might be a fog server) but then the 10.0.80.49 gives it bad IP address. That should be the IP address of a fog server or a storage node and not be blank.
-
@george1421 apologies for the crooked picture. Also I can clear up those ip addresses for you
10.0.88.49 is the DHCP/TFTP/Storage Node on interface #1
192.168.1.1 is the router address for interface #2This seems correct I think? The weird thing is the file/directory does exist when I browse to it via a web browser
(http://10.0.88.49/fog/service/ipxe/boot.php) -
@thebrennan47 It might help if you updated your picture with IP addresses but I’m going to guess what I see.
The FOG server management console is 10.0.80.49??
I could understand if 192.168.1.1 is on the deployment LAN for a storage node. Because dhcp would tell it to get the iPXE file from 192.168.1.1. The file its getting is default.ipxe. Inside the storage node 192.168.1.1 there is a file called /tftpboot/default.ipxe and it should point to the fog master server. That is where the boot.php is coming from. boot.php will determine what storage node to boot bzImage from. That is where its falling down.
-
@thebrennan47 Good you posted the iPXE code output here. To me this looks as if
FOG_WEB_HOSTis not set, seeset fog-ipon the second line is also empty. Please check in the FOG settings -> FOG configuration page on the web interface. -
10.0.88.49 was the DHCP / Storage Node. The fog management console is hosted at 10.0.88.42. I updated the default.ipxe file to point to the correct server and that fixed it! Thanks for the help with that
After a reboot on my client, I now get into the fog upload page and the process begins; but quickly terminates do to a mount failure for the /images folder. I am guessing it is a permissions issue? I am currently looking into but I figure you guys may have seen this one before so I wanted to ask real quick. Sorry for the spam of questions on this thread… I am getting really close to getting this working though it looks like
-
@thebrennan47 Boy, you are just full of good news.
OK what is 10.2.102.49? You keep throwing new IP addresses at this poor pxe booting client?
-
I actually don’t know where it is getting this IP… This particular machine has been moved in the past… so it may be possible that this is the old IP and it needs to be updated somewhere…
Any ideas where/what file this IP is being pulled from? I did a grep for it but had no luck…
-
@thebrennan47 Well I would start looking through your storage node configurations.
Slightly off topic, but along the same lines. Do you have the location plugin installed? And do you have your storage nodes assigned to a location?
-
@george1421 I haven’t set the location plugin up yet – but that does seem really useful I will likely try to do that next
I found the below post which seems like a similar issue… however the IP address field has the correct value in my case. Is this value cached anywhere? I will try rebooting the fog master node and see if that helps
https://forums.fogproject.org/topic/8828/could-not-mount-images-folder-wrong-ip-setting/3
-
@thebrennan47 Well without the location plugin FOG sees all storage nodes at the same location. So it will try to load balance between the storage nodes. So its possible that you might have a client at site D trying to pxe boot and image from Site A. Because as far as FOG is concerned they are at the same location. With the location plugin, you assign storage nodes to locations and then when you register clients, you assign clients to a location so they know what storage node to use.
-
@george1421 Alrighty I will go ahead and install the location plugin and see if that helps — but I don’t think that is the issue here because there is no machine that actually exists at this IP Address (10.2.102.49). It is an old ip address from before we moved this machine. So it seems something needs to still be updated somewhere.
I found another post that seems to mention the same problem as well. He mentioned having to change it in two places, 1: The web UI for the storage node, and 2: “a config file”
https://forums.fogproject.org/topic/6764/cannot-mount-ip-images-wrong-ip-is-used
However he doesn’t mention which config file. I have checked interfaces, .fogsettings, dhcpd.conf, the tftp, and also the /tftpboot/default.ipxe config. No luck so far though. Any idea what file he may be talking about?
-
@thebrennan47 Any news on this? The wrong IP is probably set for the Storage Node in the web UI. Go to “Storage Management” and edit the Storage Node (usually called “DefaultMember”).
