Thanks, @george1421. I haven’t worked out the DHCP problem yet, though - I just need to walk away from it for a while. I’m stumped.

Sorry for the delay, @george1421 - I’ve been battling with a DHCP issue (handing out the same IP to every machine) and it’s beaten me! I’ve just run through your test on one machine and, although it is reporting 7 urandom warnings like the 5.6 kernel, it is successfully imaging now.

@Sebastian-Roth - It is the FOG installer option that I am referring to. The only customisation of the Ubuntu 18.04 server that I am installing on is setting a static IP address on the FOG interface during installation. I’ve had the same result on 1.5.8 (installed by downloading the tar) and 1.5.9-RC2 (using Git).

@george1421 - 5.6 fails (I think the messages above were from 5.6). I think 4.19.123 was the same. 4.18.3 works, but does have “3 urandom warning(s) missed due to ratelimiting.” 4.17 gives no urandom warnings.

Would you like me to test each and record the results?

I really don’t know why this breaks it, sorry @Sebastian-Roth - I had run out of ideas and starting changing one setting at a time. It is easy to replicate, though:

• Fresh Ubuntu server 18.04 install

• Patch it

• Install FOG with no router, DNS server = the FOG server IP (with no DNS server running)

The log events start immediately on completion of the FOG installation, and don’t stop when I disable SNAPINREPLICATORGLOBALENABLED.

To avoid the issue, I reinstalled from scratch with no router or DNS server, then installed BIND9 and edited the DHCP config to add it. I haven’t tried installing BIND before the FOG installation.

I had two machines that booted successfully once on a different switch, but then never again. I did a packet capture and saw that the client wasn’t requesting an IP address when booting FogOS. I changed KERNELLOGLEVEL to 7 to get some more clues:

Starting haveged: haveged: listening socket at 3
OK
random: crng init done
random: 7 urandom warning(s) missed due to ratelimiting
starting enp2s0 interface and waiting for the link to come up
Generic PHY r8169-200:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-200:00, irq=IGNORE)
r8169 0000:02:00.0 enp2s0: no native access to PCI extended config space, falling back to CSI
No link detected on enp2s0 for 35 seconds, skipping it.
Failed to get an IP via DHCP! Tried on interface(s): enp2s0
Please check your network setup and try again

Reading up on urandom and haveged led me (eventually) to the Kernel Update function, and changing to kernel 4.18.3 now gives me a reliable boot.

I had specified the DNS server to be the FOG server, as I had intended to install DNS on the FOG server as the next step. It appears that this was causing the issue. Installing with no DNS server does not produce the error messages. Given the amount of time that I’ve spent trying to work this out, I thought that it was still worth posting.

I’ve tried a number of fresh installations of 1.5.8 on a dual-homed server (with the second NIC connected to an isolated network to be used for imaging). On completion of the installation, syslog immediately starts filling with the following block of messages - about one per second:

Aug  7 09:05:00 node2 systemd[1]: Started FOGSnapinReplicator.
Aug  7 09:05:00 node2 php[9501]: Could not open input file: env
Aug  7 09:05:00 node2 systemd[1]: FOGSnapinReplicator.service: Main process exited, code=exited, status=1/FAILURE
Aug  7 09:05:00 node2 systemd[1]: FOGSnapinReplicator.service: Failed with result 'exit-code'.
Aug  7 09:05:01 node2 systemd[1]: FOGSnapinReplicator.service: Service hold-off time over, scheduling restart.
Aug  7 09:05:01 node2 systemd[1]: FOGSnapinReplicator.service: Scheduled restart job, restart counter is at 1.
Aug  7 09:05:01 node2 systemd[1]: Stopped FOGSnapinReplicator.

I’m installing on a fresh installation of Ubuntu Server 18.04, fully patched using the following process:

sudo -i
wget https://github.com/FOGProject/fogproject/archive/1.5.8.tar.gz
tar -xzvf 1.5.8.tar.gz
cd fogproject-1.5.8/bin
./installfog.sh

.fogsettings:

## Start of FOG Settings
## Created by the FOG Installer
## Find more information about this file in the FOG Project wiki:
##     https://wiki.fogproject.org/wiki/index.php?title=.fogsettings
## Version: 1.5.8
## Install time: Fri 07 Aug 2020 09:05:30 AM UTC
ipaddress='192.168.170.1'
copybackold='0'
interface='enp2s0'
submask='255.255.255.0'
hostname='node2'
routeraddress=''
plainrouter=''
dnsaddress='192.168.170.1'
username='fogproject'
password='****'
osid='2'
osname='Debian'
dodhcp='y'
bldhcp='1'
dhcpd='isc-dhcp-server'
blexports='1'
installtype='N'
snmysqluser='fogmaster'
snmysqlpass='****'
snmysqlhost='localhost'
mysqldbname='fog'
installlang='0'
storageLocation='/images'
fogupdateloaded=1
docroot='/var/www/'
webroot='/fog/'
caCreated='yes'
httpproto='http'
startrange='192.168.170.10'
endrange='192.168.170.254'
bootfilename='undionly.kpxe'
packages='apache2 bc build-essential cpp curl g++ gawk gcc genisoimage git gzip htmldoc isc-dhcp-server isolinux lftp libapache2-mod-php7.2 libc6 libcurl4 liblzma-dev m4 mariadb-client mariadb-server net-tools nfs-kernel-server openssh-server php7.2 php7.2-bcmath php7.2-cli php7.2-curl php7.2-fpm php7.2-gd php7.2-json php7.2-ldap php7.2-mbstring php7.2-mysql php-gettext tar tftpd-hpa tftp-hpa unzip vsftpd wget xinetd zlib1g '
noTftpBuild=''
sslpath='/opt/fog/snapins/ssl/'
backupPath='/home/'
armsupport='0'
php_ver='7.2'
php_verAdds='-7.2'
sslprivkey='/opt/fog/snapins/ssl//.srvprivate.key'
## End of FOG Settings

enp2s0 is the built-in NIC and is on the isolated network with a static IP (192.168.170.1/24). This build has a second USB NIC connected to the main network (10.0.0.0/24), which has Internet access.

I have several Lenovo M73 MT-M 10B7-S01900 desktops. I am using one as a FOG server and trying to manage the others as clients. The clients successfully PXE boot to the FOG menu but when attempting to register the clients I get the following error:

starting enp2s0 interface and waiting for the link to come up

failed to get an IP via DHCP! tried on interfaces(s): enp2s0
please check your network setup and try again

FOG Version: 1.5.9-RC2
.fogsettings.txt
Note: the fog server is dual-homed interface enp2s0 is on the isolated imaging network (192.168.168.0/24) and the other on the main LAN (10.0.0.0/24). The imaging network is using FOG DHCP.

Other machines, including Lenovo ThinkPad t500, DELL Optiplex 9020, register successfully.
The M73s also successfully register on another FOG server on a separate network (single-homed with separate DHCP/DNS) that has been upgraded from 1.5.8 to 1.5.9-RC2.

Does anyone have any tips on where to start troubleshooting this?

@Sebastian-Roth - Sorry for the delay - some other unrelated issues and then a pandemic to deal with! The fix works perfectly.