Fresh install/upgrade to FOG trunk gets stuck during installation

[Msobelman]

I’ve tried that with the same results previously,

But I will go ahead and reinstall as you suggest and report back.

[Msobelman]

Just did a fresh install of 14.04.4 downloaded the latest updates and the latest Trunk.

Ran the installer and the same issue is happening.

Here’s the logs of this install.

0_1466181020702_fog_error_8157.log

0_1466181029431_foginstall.log

[Wayne Workman]

@Msobelman Its hanging at php-fpm. I’d suggest uninstalling that, reinstalling it, and restarting it. Commands:

sudo -i
service php5-fpm stop
apt-get remove php5-fpm
apt-get install php5-fpm
service php5-fpm start
service php5-fpm status

[Msobelman]

I’ve done as you suggested and it still seems to hang around the same area.

But after waiting 20 minutes it decided to let me proceed up until it failed at a different point.

It let me proceed to update the schema which I did. and after hitting enter it fails to start the DHCP server. (check install log)

here’s the error logs.

0_1466184505894_fog_error_8157.log

0_1466184512014_foginstall.log

[Quazz]

@Msobelman You need to enter a DNS server (usually same as router) for DHCP to be able to start. Add it in /opt/fog/.fogsettings

HOWEVER, it seems your server has the IP which is most commonly assigned to routers. If your router has that IP already then you’re going to have a ton of issues to get this to work.

[Msobelman]

Quazz,

I’m following this guide Fog on an Isolated Network

My FOG computer is on nothing more than an un managed switch. I’m attempting to do the install and then remove internet connectivity to it.

I also find it strange how I can install FOG 1.2.0 without issue, but the latest trunk doesn’t play nice with me.

[Wayne Workman]

DNS isn’t required for DHCP, something about the config itself is causing DHCP to fail.

Please post the contents of /etc/dhcp/dhcpd.conf and also give us the output of ip addr show

[Msobelman]

Here you go.

0_1466187672450_dhcpd.log

[Sebastian Roth]

@Msobelman Why don’t the IP/subnet mask on the console and the gui display match I wonder? Something really wrong I suppose. As well the dhcpd.conf you posted is kind of mixed up… 172.31… in the subnet class definition but 192.168… for most settings within that class?!?

[Msobelman]

I have a feeling that the way I’m going about installing the latest trunk might be causing the issue.

I’m using a Dell Optiplex 3010 as the fog sever that only has one NIC and intend to put the system on a network that has not internet connectivity.

When I install fog 1.2.0 (which works for some reason) I’m switching between DHCP and manual Ethernet configurations throughout the process to complete the install.

Example: I’ll set a manual Ethernet configuration of 192.168.1.1 etc, start the fog installation and choose my settings, then since the install reaches out to the internet during installation I’ll switch it to DHCP to grab and install the files. When it wants me to update the schema I’ll put it back to manual 192.168.1.1 to do that until the install completes.

It’s a dumb method I know, but works for 1.2.0 and what I have.

I’m trying the same thing for trunk and I guess this method I’m trying doesn’t work with it.

I’ve ordered a second NIC for this 3010 and will attempt to install it without screwing with the Ethernet settings during install to see if it will proceed correctly this time.

I’ll report back when the NIC arrives and I attempt to install Trunk again.