Default.IPXE-no such file or directory (2e008081)
-
@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.
-
@Tom-Elliott
We are using 11.101.0.0/16 network for this VLAN. All VLANs and network was planed by networks team. -
Here’s what I’m seeing:
There’s too many pictures and not enough context.
For example:
In https://forums.fogproject.org/topic/14031/default-ipxe-no-such-file-or-directory-2e008081/3?page=2# The picture is looking at fog server IP Address: 11.101.212.165 for storage, but web is at 10. (we cannot see the rest of the IP)
Next picture shows web at 192.168.1.101, and storage at 11.101.212.165 (So far both pictures show the same storage IP but not the same web IP.)
Next photo with error shows web at 11.101.149.115, but we cannot see storage (as there was no tasking applied).
Next photo with error fails with 11.101.149.115 with web also at the same machine, but also no storage IP as it’s a usb boot type.
I feel I need to inform (not trying to question your ability at all) that 11.x.x.x is public. There are only 3 private address spaces. Unless you have your router/network completely airgapped for the public address spaces, this can cause potential issues. Especially if your organization owns the 11.x.x.x IP space as you’re exposing your entire network with this.
You should be using the Private address spaces for your imaging and storage. (192.168.x.x Class C CIDR/24, 172.16.x.x Class B CIDR/16, and/or 10.x.x.x Class A CIDR/8) As this will not open potential holes and security issues within your organization as well as prevent serious issues even if all worked properly.
-
@TOXYKILLER Here’s what I find for one of your IP’s (if this is you then cool, but still a bit on the “whoa wait a minute” side)
Source: whois.arin.net IP Address: 11.101.149.115 Name: DODIIS Handle: NET-11-0-0-0-1 Registration Date: 1/19/84 Range: 11.0.0.0-11.255.255.255 Org: DoD Network Information Center Org Handle: DNIC Address: 3990 E. Broad Street City: Columbus State/Province: OH Postal Code: 43218 Country: United StatesWhat does this mean?
Well DoD own’s the IP Space in its entirety of 11.X.X.X (Including 11.101.X.X).
-
@Tom-Elliott
We unfortunately do not have comfort of static IPs (it can be added via exception but it’s really hard through the bureaucracy process and providing business justification for this)FOG add is now 11.101.128.138 (was changed by DHCP during weekend)
Some of these picture are no longer valid.
What are we using now is this 11.101.0.0/16 network.I install fog on latest ubuntu and what a i have done was this https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image/4?page=2 .
After this process task what was necessary for host registration. Registration was completed fine then i assign to this host created image and i schedule task for capturing image from host.
During this appeared this last issue. “/images/dev permission denied”
Nothing else was done on server. -
@Tom-Elliott said in Default.IPXE-no such file or directory (2e008081):
I feel I need to inform (not trying to question your ability at all) that 11.x.x.x is public. There are only 3 private address spaces. Unless you have your router/network completely airgapped for the public address spaces, this can cause potential issues. Especially if your organization owns the 11.x.x.x IP space as you’re exposing your entire network with this.
You should be using the Private address spaces for your imaging and storage. (192.168.x.x Class C CIDR/24, 172.16.x.x Class B CIDR/16, and/or 10.x.x.x Class A CIDR/8) As this will not open potential holes and security issues within your organization as well as prevent serious issues even if all worked properly.We are not using private add on our site. Only public IPs. Our company should own whole this network 11.0.0.0/8.
-
@TOXYKILLER you work with DOD Network Information Center?
-
@Tom-Elliott
Nope, I don’t work with DOD.We are using PAT for add. translation. This add. what was mentioned are not public. Sorry for little misunderstanding. -
@TOXYKILLER as long as we know the network is privately spaced and not going to cause issues, that is fine.
Then I would suggest asking your network team to give your fog server a reserved IP address. This is similar to a static IP but you wouldn’t have to keep jumping thru loops to get your server to operate, as it seems your dhcp lease times are very short. The reserved ip still resides with the dhcp server and you wouldn’t have to make any changes to the network configuration on the server for this to work.
Once you have a stationary fog server ip, I think we can get your machine up and running.
