@george1421 In the settings under TFTP Server the TFTP PXE KERNEL was set to bzImage_412. I’m assuming it should be bzImage? What’s strange is there’s no bzImage_412 file in the /var/www/html/fog/service/ipxe folder.
I ran file bzImage and got the following.
bzImage: Linux kernel x86 boot executable bzImage, version 4.19.36 (jenkins-agent@Tollana) #1 SMP Sun Apr 28 18:10:07 CDT 2019, RO-rootFS, swap_dev 0x7, Normal VGA
Not sure why it’s not showing 4.19.48 since I thought I updated it.
@george1421 I’m not actually sure why it’s using bzImage_412. I upgraded from fog 1.2.0. Maybe the bzImage didn’t get upgraded? I did go to FOG Configuration and tried the kernel update. I chose 4.19.64 TomElliott 64 and it seemed to say it updated in the web UI. The bzImage in my /var/www/html/fog/service/ipxe doesn’t seem to be newer than my upgrade date. Should it be?
Now I’m confused. That worked perfectly. It booted into the kernel you had me download, ran the hardware inventory and rebooted. I then went to the inventory tab in the web UI and it was updated. I had updated the bios on the OptiPlex 3040 so was looking for the updated bios version number and it’s there.
I did notice yesterday after I posted that disk surface test and debug tasks also hung. I just tried a disk surface test now with the downloaded kernel and it’s working too. Not sure what to think or what information would be helpful.
Thanks
I tried running the Hardware Inventory task and it seems to hang. I’m running fog 1.5.6 and was able to schedule the task on a reboot. The host rebooted and started what I think is the beginning of the Hardware Inventory task. I have the following on the screen.
iPXE 1.0.0+ (9907f) – …
Features: …
Configuring (net0 MACaddress)…ok
Received DHCP answer on interface net0
tftp://ipOfServer/default.ipxe… ok
http://ipOfServer/fog/service/ipxe/boot.php… ok
bzImage_412… ok
init.xz… ok
flashing cursor
This is on a Dell OptiPlex 3040 if that matters.
Any ideas?
Thanks
@Sebastian-Roth I’m new to this fog system we have installed so I’m not sure the old client was able to shutdown like the new one. It was more a question if I was missing something. I guess I’m not. Thanks
@Sebastian-Roth This works fine if the host is running the new client but doesn’t seem to do anything if the host is running the old client. How do I get it to trigger a shutdown on a host running the old client?
I can’t seem to figure out how to shut down a host running the old fog client. I’m running fog server 1.5.6 but I’m not finding the equivalent to power management shutdown now. I’m sure I’m just missing it but any guidance would be helpful.
Thanks