Install script fails during install on Ubuntu 22.04

[dyacishyn]

Fog installer fails at installing certificate

attached error log

fog_error_1.5.10.log

[george1421]

@dyacishyn While this isn’t a fix, but lets see if we can get past this issue.

On the FOG linux console key in

sudo mkdir /tftpboot

Then rerun the fog installer. For some reason tftp that is installed is not creating the default directory. Its possible that ubuntu is creating the directory in another unexpected location

[Sebastian Roth]

@dyacishyn Thanks for bringing this up and posting the log file. Very helpful indeed! Is this a fresh install or update from an earlier version of FOG? Pretty sure this is a fresh setup (logs show fresh MariaDB install) but just wanna make sure.

From what we see with Wayne’s installer tests Ubuntu 22.04 should work. As well I have done dozens of install/updates on 22.04 in preparation of the new release.

Looks like the Ubuntu install was not up to date to start with. Usually not an issue but I still think it’s worth to be aware of:

The following packages will be upgraded:
  apport apt apt-utils base-files cloud-init cryptsetup cryptsetup-bin
  cryptsetup-initramfs distro-info-data dmidecode fwupd fwupd-signed gzip
...

But then I am not sure why we see useradd: warning: the home directory /home/fogproject already exists. if this is a fresh setup?!

cp: cannot stat ‘/tftpboot/*’: No such file or directory

This error message is normal on a fresh install and can be ignored (see in the script code.

Fog installer fails at installing certificate

This is a bit missleading. I would think it’s actually failing when trying to compile the iPXE binaries with the self signed certificate as you seem to have selected for a HTTPS enabled setup. So please upload fog_ipxe-build_1.5.10.log - found in the same directory where you got the install log from.

[dyacishyn]

@Sebastian-Roth This is a fresh install, installed from /home/fogproject

fog_ipxe-build_1.5.10.log

[Sebastian Roth]

@dyacishyn The end of the log file is just garbage. Any idea what went wrong? Maybe the disk is running out of space?

[dyacishyn]

@dyacishyn HHMMM this disk isn’t running out of space… I’ll head down to my server room ad have a look at the output on the console.

[rodluz]

This post is deleted!

[dyacishyn]

@dyacishyn it appears that my main Hard Drive had failed… ‘sigh’ time to rebuild again…

[Sebastian Roth]

@dyacishyn Too bad. Hope you have a recent backup of the database and the images.

Marking as solved as we know what was causing the described issue.