@sebastian-roth i checked the version of FOG on the nodes. All are reporting:
define(‘FOG_VERSION’, ‘1.5.9’);
/var/www/fog/lib/fog/system.class.php: define(‘FOG_VERSION’, ‘1.5.9’);
Attached is another image of a machine with a deploy task. This one pointing to a different node.
@Sebastian-Roth Looking at the web-GUI and checking the list of installed plugins, there are zero installed plugins.
Attached is screen grab of all the storage nodes that are listed in the FOG web ui.
This issue happens when pxe booting into any machine against any FOG storage node.
First @Sebastian-Roth, thank you so much for your continued assistance with this.
On double checking it is FOG version 1.5.9.201
Sadly, I do not know the previous version that was being ran before the jump to the version listed above.
How would I check to see which plugins are enabled/installed.
There are storage nodes being used. The storage nodes have all be updated to the same version. They are also all reporting back with connections to the main database. Also verified by re-running the installing and getting the connect to database successful message in the install process.
@sebastian-roth said in Could not boot: no such file or directory:
http://x.x.x.x/fog/service/ipxe/boot.php?mac=98:90:96:c5:16:46
FOG version 1.5.9 RUnning on CentOS 7.
here is the full output as requested:
#!ipxe
set fog-ip 10.51.1.52
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
kernel http://10.65.2.20/fog/service/ipxe/bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://10.51.1.52/fog/ consoleblank=0 rootfstype=ext4 nvme_core.default_ps_max_latency_us=0 mac=98:90:96:c5:16:46 ftp=10.65.2.20 storage=10.65.2.20:/images/ storageip=10.65.2.20 osid=9 irqpoll hostname=LAB13771WDTA chkdsk=0 img=InstructionalV22_1 imgType=n imgPartitionType=all imgid=125 imgFormat=0 PIGZ_COMP=-9 hostearly=1 type=down
imgfetch http://10.65.2.20/fog/service/ipxe/init_32.xz
boot
@george1421 Thank you for the response. The target computer receives this error when attempting to access the pre deployment screen. (Where a machine can be registered, deploy image, quick host deletion, etc).
Checking the storage node manager for the storage node this machine is referencing has the correct IP address in the field.
@george1421 Thank you for the suggestions. I went and checked those two settings and they have the correct FOG server IP address in both of the fields. I noticed the missing IP in the 3rd URL and was also wondering why there was nothing being applied there.
@george1421 Thank you for the suggestions. I went and checked those two settings and they have the correct FOG server IP address in both of the fields. I noticed the missing IP in the 3rd URL and was also wondering why there was nothing being applied there.
Recently updated FOG nodes to most recent version. When attempting to image was presented with the following error message. 
Any idea what file it is trying to locate but unable to?
