Default.IPXE-no such file or directory (2e008081)
-
@TOXYKILLER Well from your picture the first thing I noticed is that your fog server is at 10.<something off the screen> but your storage ip is 11.101.212.165 is that correct?
-
@george1421
Since our last conversation i revoke a little bit topology (for more similar to production network).Now i don’t have static IPs and i using router as DHCP server.Server IP is now 192.168.1.101/24
Client have 192.168.1.100/24
Gateway 192.168.1.1So now when i boot via usb stick i put IP addres of sever.
and here is full error screen
here are logs from
/var/log/apache2/error.log
and here are from var/log/syslog | grep php
-
@TOXYKILLER Well I was going to say that it appears your dhcp server isn’t sending out the next-server value so iPXE is asking for it. But you deleted your post. Depending on the router, some soho routers send the next server address as them selves even if you set it to something else.
-
@george1421
We now for this testing purpose using tp-link TL-MR6400.I check router setting and about DHCP is almost non existent settings so you advice about this issue is a create own linux base DHCP server ? -
@TOXYKILLER If you want to continue to use your existing dhcp server that is possible. You just need to install DNSMASQ onto your FOG server. The dnsmasq configuration will only provide pxe boot information. All other network details come from your main dhcp server. The only issue is if your pxe booting clients are on a different subnet than the fog server. If that is the case, you will need to update a setting in your network configuration. On your vlan/subnet router you will need to add the FOG server’s IP address as the last host in your router’s dhcp-helper/relay service. I didn’t mention this before, because you said you had no access to any infrastructure changes. Here is the tutorial for installing dnsmasq onto your FOG server. The instructions are centos/rhel specific but the only real difference for Ubuntu distro is to use apt-get instead of yum: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server
-
@TOXYKILLER As mentioned already the storage node IP seems to be different. Did you setup the server using that IP and then changed it later on? https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address
-
@Sebastian-Roth
I try it with via using web settings still not working also i tried .fog settings file but it’s seen won’t work at all(after install i don’t have this file created and also file tftpboot missing as well). I change this setting and try create usb again via this manual https://wiki.fogproject.org/wiki/index.php?title=USB_Bootable_Media . -
@TOXYKILLER Sorry for not answering but there was lot’s to do before X-Mas and I lost track of this. The USB boot method in the wiki is kind of old. Better you take a look at this: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image (page 2!)
-
@Sebastian-Roth
Hi thank you for this manual it’s help. I can now register host but i can’t capture image from PC (i also choose in fog this options in host list). It’s seems i have issue with “/tmp/himfo.txt”. I try find this file but it’s doesn’t exit.
-
@TOXYKILLER If you are using the USB boot method that boots via grub. You missed one of the caveats with this method. You need to schedule the task first within the FOG web ui then pick option 1 on the grub menu. What that error is saying, “hey you want to image, but I don’t have any task to tell me what to image”
Schedule the task first in the fog ui then pxe boot the computer and you should be good.
-
@george1421
Thanks i can preform now registration and schedule image capture. But i have issue with fog “/images/dev permission denied”
I try find this folder via this commands showmount -e and find but i can’t find anything with this direct path and name.
-
@TOXYKILLER So what does
showmount -e 127.0.0.1give you?Also that directory will be on the fog server in /images/dev, so show us the results of
ls -la /images -
@george1421
Hi, here is results of this two commands.
-
@TOXYKILLER Comparing this to your other pictures I feel you’ve misunderstood George. Please run those two commands on your FOG server terminal!
-
@TOXYKILLER You are running those commands on the FOG server? If so is that really the fog server because its not setup correctly.
-
@george1421
Yes this is my FOG sever. I know it’s a little bit misleading name for server. This name is only for testing purpose. -
@TOXYKILLER
I’m really at a loss.
In one picture, the hostname appears to be fog-server, and in the latest one it appears to be fog-desktop.
Did you install a new fog server instance on another machine?
As others have pointed out, you don’t have an install (or at least a completed installation) on the machine labelled fog-desktop.
-
Also,
Based on what I’m seeing, your FOG Server is IP: 11.101.149.115, which is a publicly accessible IP address, is this by design? I’m not quite sure that you’d be able to route NFS traffic unless your router/firewall admin’s have enabled this (and it’s not pretty or easy as NFS uses a lot of ports - and they’re random)
-
@Tom-Elliott
I had i little issue i try some fix from forum and my system won’t boot properly so i decided new install like before and now i made a copy of this system to prevent this situation. -
@TOXYKILLER said in Default.IPXE-no such file or directory (2e008081):
I know it’s a little bit misleading name for server.
In my case I didn’t notice or care about the name. The issue I have is IF fog is installed, the installer will create a /images directory as well as /opt/fog directory. Also the output of the exports command is blank. I would say that the fog installer was never run or never completed running on this system.
