Cannot deploy images

[george1421]

@george1421 So far we found in the pcap that the client is trying to download bzImage412 and the fog server is replying with file not found.

[george1421]

@tom Well that wasn’t what I expected (it looks good).

Lets try one more URL call: http://<fog_server_ip>/fog/service/ipxe/boot.php?mac=<mac_address_of_target_computer>

[george1421]

@george1421 Just for clarity this is what we see in the pcap

Note that packet 56 asking for bzImage412 and then in packet 58 the FOG server says 302 not found.

[Tom]

@george1421

#!ipxe
set fog-ip 192.168.2.196
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://192.168.2.196/fog/service/ipxe/bg.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.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 10000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || 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=127000 web=192.168.2.196/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.2.196:/images/ storageip=192.168.2.196 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=127000 web=192.168.2.196/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.2.196:/images/ storageip=192.168.2.196 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.deployimage
login
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
: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
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.2.196/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.2.196:/images/ storageip=192.168.2.196 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://192.168.2.196/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot

[george1421]

@tom OK this isn’t getting us to the answer. Not your fault, I think “fog” is helping us by hiding the answer.

Can you go to the FOG webgui and look at the FOG Configuration->FOG Settings. Then in FOG Settings look at these values:
FOG_TFTP_PXE_KERNEL (suspect is wrong) should be bzImage
FOG_TFTP_PXE_KERNEL_32 (probably right)

[Tom]

@george1421

[george1421]

@tom Well as they say… There you go. You found the smoking gun.

Did someone try to create a custom kernel for some reason?

[Tom]

@george1421
Not that I am aware of. I was on vacation.
So, what are the changes I need to make?

Thanks,
Tom

[george1421]

@tom Well I would start out by changing that value of bzImage412 in FOG_TFTP_PXE_KERNEL back to the default of bzImage. Then reboot your target computer and see if you can register it.

[Tom]

@george1421
I will tested in the morning and provide feedback.

Thanks for all the help.

Tom

[Tom]

Changed the entry to bzimage4123 and it seems to be working fine.
Thank you for all your help.

You guys ROCK!

Tom

[Sebastian Roth]

@Tom Why the heck you using bzimage4123 now or was this just a typo?

[Tom]

@sebastian-roth

I cannot say how it was changed. I never touch the settings, unless it is a fresh install which was not the case.

Tom

[Sebastian Roth]

Nevermind, though this is definitely not something FOG did by itself… case closed.