@thebrennan47 That helps out quite a bit. I thought there was a bit more going on here than I originally imagined.

You need to change up your configuration. Your storage node is acting as a gateway between the fog server and the target systems. You need to change the served subnet on each storage node. Each storage node needs to be connected to a unique subnet. On the surface you have a routing problem not a fog problem.

Consider if you are using subnets 192.168.1.x on each storage node. If a computer on SN1 talks to the fog server, and a computer on SN2 talks to the fog server and each has the same subnet, how will the fog server know where/who to respond to.

So how to fix it? Give SN1 imaging network an IP subnet of 192.168.1.x./24. Give SN2 imaging network an IP subnet of 192.168.2.x/24. Give SN3 imaging network an IP subnet of 192.168.3.x/24.

Now go to your internet router and create a static route (or you can do this on your FOG Master node) that describes the subnets beyond each storage node. Like

ip route add 192.168.1.0 mask 255.255.255.0 via {SN1 LAN interface}
ip route add 192.168.2.0 mask 255.255.255.0 via {SN2 LAN interface}
ip route add 192.168.3.0 mask 255.255.255.0 via {SN3 LAN interface}

You will need to change the dhcp server settings on each SN too to match their respective imaging network range.

Once you have routing and unique IP addresses in play FOG should work a bit better.

@thebrennan47 The 500 error indicates you have an issue in your php.

You might want to review the apache error log to see if it will give you a clue to the issue.

@sebastian-roth @george1421

Sorry for the late response on this guys.

The issue with this turned out to be with the OEM recovery partition that came with our dell machines. For whatever reason fog didn’t like it. Removing this partition fixed the issue and we now have the new fog server, and all the new hardware synchronizing and imaging correctly.

Thank you guys again for all your assistance in this thread (and the others). This forum has been extremely helpful

@thebrennan47 why don’t you explain more how you fixed it?

Case solved! Thanks again to both of y’all @george1421 @Wayne-Workman

@thebrennan47 Any news on this? The wrong IP is probably set for the Storage Node in the web UI. Go to “Storage Management” and edit the Storage Node (usually called “DefaultMember”).

@Quazz said in Install script errors:

I’m wondering if Ubuntu updated Bash to be a bit different, hmmm.

They didn’t. The installer is tested on Ubuntu every day, you can see the test results here: http://perpetuum.io:20080/fog_distro_check/installer_dashboard.html

@thebrennan47 said in Fog freezes on boot at kernel_thread_helper:

We want to avoid upsetting our production environment if at all possible

I can understand your concern about not wanting to destabilize your environment.

But realize that the Windows 10 train is heading towards your environment very soon, so you WILL have to upgrade sooner or later. Also the 7040 is the last of the sky lake models the next generation are on kaby lake. Microsoft has intentionally crippled windows 7 to not run on kaby lake hardware (even though it ran fine earlier this year). So moving forward you will have to install win10 if you purchase new hardware. That day is coming. I’m only telling you what is coming down the road so you can plan for it.

As for ubuntu 12.04 that reached end of support in April of this year. So you will not receive any security updates for it if any are detected. That is also a pressure for you to upgrade.

The kernels that Tom posted about may work on the newer hardware, surely FOG 1.4.2’s kernels will run on that hardware. It might not integrate with FOG 0.3x very well, but it should run on the 7040 ok (I’m doing that today).