r7478 Advanced Boot Menu not worked

[sgennadi]

I have 3 advanced menu item in the boot menu list, after svn update
First menu with password not worked. Second worked fine. Third
then i choose menu item i recieve error (see picture)… Menus worked fine for a long time ± 6 six month ( and I don’t do any changes)

[Tom Elliott]

@sgennadi Still, error logs? anything we can use to help figure out the issue? My guess, if I had to have one, is your pxe_menu_timeout value is not set currently. Because of this the menu is not setup correctly. Again this is just a guess, but error logs would certainly go a long way, and is there a real need for all this to be in the advanced menu? I ask because trunk allows you to put this all on the main menu screen now. Maybe it will have better luck that way?

[sgennadi]

@Tom-Elliott
Which log exactly you need?

[Tom Elliott]

@sgennadi apache error logs.

[Sebastian Roth]

@sgennadi If you don’t know where to find those logs check out the signature below my message…

I just copy&pasted your script into my advanced menu config and it works like a charm.

[sgennadi]

I know what is my script worked and must work but no…

when I choose Diagnostics
0_1462429656458_error_log

[sgennadi]

I made new menu from faq sample - not worked

Maybe problem with html parser

I made new menu Bios with description Bios & Firmware

But

Previous fog version now problem with “&” and description

[Quazz]

Sometimes the code looks fine, but the structure is actually not filled in properly which causes stuff like this. I’m guessing something went wrong here :

item return return to previous menu
choose --default return --timeout 15000 target && goto ${target}
:wd

It’s probably formatted accidentally something like

item return return to previous menu
choose
 --default return --timeout 15000 target && goto ${target}
:wd

So expand the code box and double check all that.

[sgennadi]

Centos 7 (latest updates ) If I check boot.php
http://x.x.x.x/fog/service/ipxe/boot.php I see problem with ampersand symbol $

[Tom Elliott]

@sgennadi What @Sebastian-Roth is saying, is your script works perfectly fine. What we need is error logs to helps us at least with a starting point of what is going on.

[Tom Elliott]

@sgennadi What HTML parser?

Somethings gone wrong with how that information is stored (which is pretty obvious), but FOG has not caused that, at least not directly.

[Andy Abplanalp]

@sgennadi is your path correct? You’re defining {boot-url} but you’re using {fog-ip} in the path to your image files

[sgennadi]

Path correct , problem with & in the script and how it stored