iPXE no such file or directory
-
Just updated to trunk 5229. Now when booting I get an error message that states:
/NULL … No such file or directory
loading boot.php i see the iPXE output but near the top it looks like it is missing the IP and directory for the fog server, see below.
#!ipxe
set fog-ip 172.16.101.111
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}Is there anything I can do to fix this?
-
@technokami Could you send us a picture of the error?
-
What did you update from that? Meaning, what version did you update?
-
I upgraded from a previous trunk version but I cant remember which one. Attached is a photo of the error.
-
If you access http://172.16.101.111/fog/service/ipxe/boot.php?mac=34:17:eb:a2:a9:86 from a browser in another client on your network, what do you see? Is it just those four lines you posted already? Don’t think so. Please post the full output you see in the browser.
-
when I visit that page this is the output I get:
#!ipxe
set fog-ip 172.16.101.111
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
#!ipxe
kernel NULL loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.16.101.111/fog/ consoleblank=0 mac=34:17:eb:a2:a9:86 ftp=172.16.101.111 storage=172.16.101.111:/images/dev/ storageip=172.16.101.111 web=172.16.101.111/fog/ osid=7 consoleblank=0 irqpoll hostname=F2B3422 chkdsk=0 img=UpdatedWindows81 imgType=n imgPartitionType=all imgid=5 imgFormat= PIGZ_COMP=-9 adon=1 addomain=NULL adou=NULL aduser=NULL adpass=NULL fdrive=NULL hostearly=1 pct=5 ignorepg=1 type=up NULL
imgfetch init_32.xz
boot -
@technokami said:
kernel NULL
That line suggests to me that the kernel didn’t download. Can you try to reinstall?
-
Can you access the webinterface an check the hosts settings (Host Management -> edit host). See if there is any string (whitespaces??) in the “Host Kernel” field. Make sure this is completely empty. Then go to FOG Configuration -> FOG Settings -> TFTP Server. FOG_TFTP_PXE_KERNEL should be ‘bzImage’ and FOG_TFTP_PXE_KERNEL_32 should be ‘bzImage32’. I guess yours are empty?!
-
@technokami this was my fault. Basically, I was attempting to ensure id field always had a value higher than 0. Research suggested making sure fields without data passes incorrectly to MySQL. I learned, quickly, that this was not the case and corrected it from the code. We sanitize all values and fields and rather that setting the value to NULL it set it to a string with the word NULL. Simplest fix would be to revert the db. Before I made the NULL attempt, I added the db backup on updates/installs. This means you can find the backup and revert the db to that. This should fix the issue you’re seeing. I assure you it was not my intention to break the db in such a manner. I do know nothing was corrupted, but updates to an item where the fields were blank should appear on their relevant fields as literally the word NULL.
-
Well then it probably says ‘NULL’ in the hosts settings (‘Host Kernel’). Take a look there and make this field empty again.
-
@Tom-Elliott said:
@technokami this was my fault. Basically, I was attempting to ensure id field always had a value higher than 0. Research suggested making sure fields without data passes incorrectly to MySQL. I learned, quickly, that this was not the case and corrected it from the code. We sanitize all values and fields and rather that setting the value to NULL it set it to a string with the word NULL. Simplest fix would be to revert the db. Before I made the NULL attempt, I added the db backup on updates/installs. This means you can find the backup and revert the db to that. This should fix the issue you’re seeing. I assure you it was not my intention to break the db in such a manner. I do know nothing was corrupted, but updates to an item where the fields were blank should appear on their relevant fields as literally the word NULL.
Thanks for the info. I replaced the NULLs with blanks and everything is back up and running. @Sebastian-Roth you were right as well there was a literal NULL string in the host settings in every field that was normally blank.
-
@technokami Great to hear that you got it working again! Thanks for reporting back and for letting us know about this issue.
