FOG 1.6, identified problems

[lebrun78]

Hello,
I decided to install my new server to 1.6. It takes a lot of testers!
My server is in Centos 8.0

Here are some problems I had:

• where could I dowload client installer from the web intreface ?

• /tftpboot/default.ipxe is not updated in the web interface

• I use advanced ipxe to access mdt server. I have a problem with accessing to advanced ipxe
  In legacy boot I get a black background with slider
  In UEFI, I get

Could not boot! Exec format error (http://ipxe.org/2e008081)
Chainloading failed. hit 's' for the iPXE shell

[Sebastian Roth]

@lebrun78 May I ask you some questions on this?

/tftpboot/default.ipxe is not updated in the web interface

What do you mean by that? As far as I know we never had an option to make adjustments to that file in the web UI!?

EDIT: Found and fixed an issue in the advanced menu code just now. Please re-pull the latest and re-run the installer.

[lebrun78]

@Sebastian-Roth said in FOG 1.6, identified problems:

@lebrun78 May I ask you some questions on this?

/tftpboot/default.ipxe is not updated in the web interface

What do you mean by that? As far as I know we never had an option to make adjustments to that file in the web UI!?

On a other test with Version 1.5.7.49, I did have to edit this file to change the adress of the chained server

I use advanced ipxe to access mdt server. I have a problem with accessing to advanced ipxe

Please post your advanced menu code here so we can have a look!
Here it is:

:MENU
menu
item --gap -- ---------------- iPXE boot menu ---------------- 
item WIN10MDT1903 Boot MDT-Win10-1903
item WIN10MDT64BIT Boot MDT Win10 64 bit iso
item Fedora Installation Fedora
item shell ipxe shell
item return return to previous menu
choose --default WIN10MDT1903 --timeout 5000 target && goto ${target}
:Fedora
kernel http://${next-server}/linuxboot/vmlinuz ks=http://${next-server}/linuxboot/distribs-Linux/Fedora25/anaconda-ks9.cfg
initrd http://${next-server}/linuxboot/initrd.img
boot
:WIN10PE64BIT
cpuid --ext 29 && set arch amd64 || set arch x86
kernel http://${next-server}/wimboot
initrd http://${next-server}/winpe/${arch}/media/Boot/BCD BCD
initrd http://${next-server}/winpe/${arch}/media/Boot/boot.sdi boot.sdi
initrd -n boot.wim http://${next-server}/winpe/${arch}/media/sources/boot.wim boot.wim
boot
:WIN10MDT64BIT
cpuid --ext 29 && set arch x64 || set arch x86
kernel http://${next-server}/wimboot
initrd http://${next-server}/mdtboot/${arch}/media/Boot/BCD BCD
initrd http://${next-server}/mdtboot/${arch}/media/Boot/boot.sdi boot.sdi
initrd -n boot.wim http://${next-server}/mdtboot/${arch}/LiteTouchPE_${arch}.wim boot.wim
boot
:WIN10MDT1903
cpuid --ext 29 && set arch x64 || set arch x86
kernel http://${next-server}/wimboot
initrd http://${next-server}/mdtboot/${arch}/media/Boot/BCD BCD
initrd http://${next-server}/mdtboot/${arch}/media/Boot/boot.sdi boot.sdi
initrd -n boot.wim http://${next-server}/mdtboot/${arch}/LiteTouchPE_1903.wim boot.wim
boot

In legacy boot I get a black background with slider

Can you take a picture of that and post here?

[Sebastian Roth]

@lebrun78 Sorry, updated my post…

Found and fixed an issue in the advanced menu code just now. Please re-pull the latest and re-run the installer.

On a other test with Version 1.5.7.49, I did have to edit this file to change the adress of the chained server.

So what is the difference between 1.5.7.49 and working-1.6?

[lebrun78]

@Sebastian-Roth said in FOG 1.6, identified problems:

is the difference between 1.5.7.4
Version 1.6 (for me): ChannelAlpha | Version1.5.7.733

With your modification, advanced menu works fine

where could I dowload client installer from the web interface ?

[Sebastian Roth]

@lebrun78 said:

where could I dowload client installer from the web interface ?

As Tom is mostly working on this I can’t tell you from the top of my head. @Tom-Elliott?

Though I can give you an official link: https://github.com/FOGProject/fog-client/releases/download/0.11.16/SmartInstaller.exe

[lebrun78]

New problem
When I try to deploy via task , deploying works.
But when I try to deploy by boot menu on the client, I get:

http://fogus/fog/service/ipxe/boot.php...  HTTP 5xx Server Error (http://ipxe.org/1d0c6598)
Could not boot: HTTP: 5xx Server Error (http://ipxe.org/1d0c6598)

Thank you for your help,

Arnaud

[Sebastian Roth]

@lebrun78 Please take a look at the apache and PHP-FPM error logs (see my signature) and post here. With 5xx server error we should get a proper message in the logs as well.

[Tom Elliott]

FOG Client url is:

http://<ipoffog>/fog/management/index.php?node=client

You can go to this url directly.

The other way to access is to choose Client Settings -> Home Tab -> Then click the click here link.

[Tom Elliott]

Also,

Added Link directly now to the Menu bar.

Hopefully that helps make it so much more accessible.

[lebrun78]

@Sebastian-Roth said in FOG 1.6, identified problems:

@lebrun78 Please take a look at the apache and PHP-FPM error logs (see my signature) and post here. With 5xx server error we should get a proper message in the logs as well.

Hello Sebatian
Here it is:
[12-Nov-2019 08:41:49 UTC] PHP Warning: ftp_login(): Login incorrect. in /var/www/html/fog/lib/fog/fogftp.class.php on line 274

@Tom-Elliott said in FOG 1.6, identified problems:

Also,

Added Link directly now to the Menu bar.

Hopefully that helps make it so much more accessible.

Thank you Tom-Elliott

[Tom Elliott]

@lebrun78 This error makes little sense.

I would understand the PHP error if you were actually in FOS environment, but you’re not. Your getting error 500 when loading the boot.php file.

Can you have a machine go to the boot.php file and tail the php-fpm error log? This should present the problem immediately. The boot.php doesn’t call FTP at that point, so this message seems unrelated (though would need to be fixed as well).

[lebrun78]

@Tom-Elliott
I have nothin (so no error) in /var/log/php-fpm/www-error.log and /var/log/php-fpm/error.log when running boot.php on the client

[Tom Elliott]

@lebrun78 said in FOG 1.6, identified problems:

http://fogus/fog/service/ipxe/boot.php

So if you go to the above url directly all returns properly?

[lebrun78]

@Tom-Elliott
It seems ok:

#!ipxe
set fog-ip 148.60.15.217
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://148.60.15.217/fog/service/ipxe/bg-plateforme.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.deployimage Deploy Image
item fog.multijoin Join Multicast Session
item fog.advancedlogin Advanced Menu
choose --default fog.local --timeout 3000 target && goto ${target}
:fog.local
chain -ar ${boot-url}/service/ipxe/grub.exe --config-file="rootnoverify (hd0);chainloader +1" || goto MENU
:fog.memtest
kernel memdisk initrd=memtest.bin iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://148.60.15.217/fog/ consoleblank=0 rootfstype=ext4 storage=148.60.15.217:/images/ storageip=148.60.15.217 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://148.60.15.217/fog/ consoleblank=0 rootfstype=ext4 storage=148.60.15.217:/images/ storageip=148.60.15.217 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.deployimage
#login
params
param mac0 ${net0/mac}
param arch ${arch}
param hostname ${hostname}
goto host_${hostname} || goto autres
:host_bug
:host_win10-3
:host_i207m01
:host_i207m02
:host_i207m03
:host_i207m04
:host_i207m05
:host_i207m06
:host_i207m07
:host_i207m08
:host_i207m09
:host_i207m10
set username i207stud
set password coucou
params
param username i207stud
param password coucou
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
goto fin
:autres
login
params
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fin
param sysuuid ${uuid}
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
param sysuuid ${uuid}
:fog.advancedlogin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param advLog 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
param sysuuid ${uuid}
:bootme
chain -ar http://148.60.15.217/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot

[Tom Elliott]

@lebrun78 You have a custom Boot.php file?

Maybe the output from PHP is perfect, but how IPXE is interpretting the information is causing the issue.

I’m very confused what you’re trying to do with your menu. And it’s almost difficult to break it down to it’s constituant parts.

Can you reset your “Deploy” ipxe menu to:

params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme

and see if things are working. Feel free to copy your original menu items too, so you don’t lose it, but my guess is the error you’re seeing is in your customization.

[lebrun78]

@Tom-Elliott

Hello

I tried by resetting the menu; but that does not work, the deploy menu runs in a loop.

The configuration on my test server was recovered by restoring the server’s mysql database in 1.4.4, so the boot menus are normally good

[Sebastian Roth]

@lebrun78 said in FOG 1.6, identified problems:

The configuration on my test server was recovered by restoring the server’s mysql database in 1.4.4, so the boot menus are normally good

Uhhhhmmm, not a good idea. FOG 1.6 is quite different to 1.5.x and even more to 1.4.4!! I am pretty sure your setup is now totally messed up with a DB recovery form 1.4.4 state.

When you initially setup the 1.6 server, did you install plain from scratch or did you start from a copy of an old server? It’s very hard to help if we only know part of what exactly you did.

[lebrun78]

it’s a brand new server, (new hardware, new centos 8.0 distribution) except the fog database I restored.
I would like to keep machines, images, snapins configurations

[lebrun78]

@Sebastian-Roth
with the restoration of the base, it seemed to work well.
Should I restart from scratched, installed and import from 1.4.4 export files for images, hosts, snapins?