I didn’t see a forum here for generic questions not exactly related to fog so I figured I’d try here. We’ve got a Ubuntu 18.04 server running fog 1.5.6. It was upgraded from Ubuntu 10.04 and fog was upgraded from 1.2.0. It also runs our NT4 style Samba domain. We’re in the process of upgrading all our host machines from Windows 7 to Windows 10 and they have issues connecting to the NT4 domain. We’re looking to migrate from Samba NT4 to Samba AD. We can’t seem to find good instructions on migrating under Ubuntu 18.04. I’ve found instruction on Samba’s site but they’re not Ubuntu specific and I’ve found instructions on creating an AD on Ubuntu 16.04 but not migrating. Has anyone done this before? If this is too off-topic feel free to remove this post. Just figured I’d ask.

Thanks

@george1421 All my hosts seem to be working fine now.

Should I just remove the useless symlink?

Thanks for the help.

@george1421 Right now I’ve got all the web files in /var/www/html/fog. Inside that directory there’s a symlink called fog pointing to /var/www/html/fog (same thing). Not sure why. I’m on Ubuntu 18.04. How should it be set up so upgrades work properly?

I’ll have to test tonight to make sure the hosts are booting correctly and that the compatibility test works but I’m pretty sure they will now.

@george1421 Turns out the TFTP PXE KERNEL DIR variable was set to /var/www/fog/service/ipxe instead of /var/www/html/fog/service/ipxe/ which explains why the kernel wasn’t updating. Now it is. And I’ve got 4.19.64 now. I’m not sure why it was set wrong in the first place. And I agree, I don’t know why hosts were still booting. I’d get the fogproject splash page with a 3 second countdown on booting the first hard drive and then they would boot normally. A memory test seemed to work from the splash page but nothing else that I tried.

@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?