Add an menu item thruogh web GUI

[Tom Elliott]

@jgallo that option has been there since 1.4 I believe.

[klkwarrior]

@jgallo We do see the deploy image option yet it always errors out with “failed chainloading -s”. I can get the full error when I use it today.

[klkwarrior]


[Tom Elliott]

@klkwarrior please try reuploading but wait until you see the picture load before submitting.

[klkwarrior]

[Tom Elliott]

@klkwarrior did you start creating your own menu items?

[klkwarrior]

@tom-elliott no, this is the current state of deploy image. I have tried looking up this error and always get sent to ipxe.org/cmd. From other co-workers of mine, they say this started to happen after we had our Fog Server updated. I was not here when this happened.

[klkwarrior]

@tom-elliott Would getting the boot.php file help diagnose this issue? if so i can provide that.

[Sebastian Roth]

@klkwarrior Even better, please open the following URLs in your browser and provide the full output you get here: http://10.0.0.5/fog/service/ipxe/boot.php and http://10.0.0.5/fog/service/ipxe/boot.php?mac=xx:xx:xx:xx:xx:xx (put in the client PC MAC address instead of xx:xx:xx:xx:xx:xx)

[klkwarrior]

@sebastian-roth 0_1532608066897_boot.txt 0_1532608082004_boot_mac.txt

[Sebastian Roth]

@klkwarrior Can’t see where this -S is coming from. Can you please capture the HTTP traffic when this is happening?

• Get your client ready but don’t start yet. Make sure you know the IP address it receives on DHCP later on.
• install tcpdump on your FOG server (e.g. sudo apt-get install tcpdump)
• run tcpdump: sudo tcpdump -w item_issue.pcap host x.x.x.x (put in the client’s IP address instead of x.x.x.x and leave the command running)
• boot up the client till you see the error message on screen - then stop tcpdump (ctrl+c), upload the item_issue.pcap file to some server/cloud and post a link here.