DHCP problems on storage nodes

[Greg Plamondon]

@george1421

ok, I have the S40network modiefied and the init repacked. do I need to run the same command for testing?

[Greg Plamondon]

@george1421

I am getting an error in the S40network file.

[george1421]

@greg-plamondon Whelp, that’s why I’m not a programmer

Here is what needs to be fixed, sorry.

This is the bad line

if [ $ustat -eq 0 && $cstat -eq 0 ]; then

This is what it should have been

if [[ $ustat -eq 0 && $cstat -eq 0 ]]; then

Awe, crud and then the next errors you will find are a few lines down.

		if [ $ustat -eq 1 ]; then
			echo "## DHCP failed on $iface ##"
		fi
		if [ $cstat -eq 1 ]; then
			echo "## The Master FOG server failed responded to our query ##"
		fi

need to have the brackets too

		if [[ $ustat -eq 1 ]]; then
			echo "## DHCP failed on $iface ##"
		fi
		if [[ $cstat -eq 1 ]]; then
			echo "## The Master FOG server failed responded to our query ##"
		fi

[Greg Plamondon]

@george1421

[Greg Plamondon]

@george1421

My question is if the connection is good “## We have an IP address on eth0 and the Master FOG server responded to our query ##” Why does it then disconnect the eth0 interface and attempt to obtain an IP when it already has one that is working?

[Greg Plamondon]

@george1421

now if I issue a: /etc/init.d/S40network restart
I get this:

[george1421]

@greg-plamondon That looks perfect. If you now key in fog you can single step through deployment. Or just cancel the task on the fog server and then pxe boot this again, the vm should image. At least from a networking point everything is golden.

Is there any chance to do this on one of the broken systems?

You will see if there is an error, it will loop through this code 3 times then give up. IN this case it only when through once because it worked.

[Greg Plamondon]

@george1421

hmmm

[Greg Plamondon]

@george1421
here is a video:
Youtube FOG

[george1421]

@greg-plamondon just for clarity is this on the VM or a physical host?

[Greg Plamondon]

@george1421

this is a VM on the same host as the fogserver.
the physical PC’s do the same thing I just can’t get screen-caps of them.

[george1421]

@greg-plamondon looking at your video, it almost appears that there are 2 scripts running to start the networking. We see clearly that the S40network is executing because it has our ## messages. But the second “unknown script at this time” doesn’t print out our ## messages. That tells me there is some other code running not in S40Network that is trying to reinit the network adapter. I guess I need to do a bit more digging here.

[Greg Plamondon]

@george1421

oops, lol I copied the moved the S40network to S40network.old

[Greg Plamondon]

@george1421
ok removed the S40network.old, new video

[george1421]

@greg-plamondon Its the same issue again, a second set of dhcp functions are being called. Did you take the S40network.old out of the init.d directory? Actually you can delete it since you saved the original init.xz image anyway.

[Greg Plamondon]

@george1421
yes its removed.

[Greg Plamondon]

@george1421

I dont know what the difference is from the init.xz that is on the main fogserver and the one that is on the storage node but I copied the init.xz from the main fogserver to the storage node and it works now? what gives?

[george1421]

@greg-plamondon There is/was a change in the init.xz files between FOG 1.4.4 and 1.5.0RCx The 1.5.0RCx now supports both http and https transactions throughout, where 1.4.4 kind of - sort of - supported https transactions, but not always.

When you upgraded to 1.5.0 on your main server, did you upgrade all of the storage nodes in your fleet? The fog kernel (bzImage and init.xz) need to be matched to the version of FOG that is installed.

[Greg Plamondon]

@george1421

yes the fogserver and all nodes are on the same build.

[Greg Plamondon]

Running Version 1.5.0-RC-10
SVN Revision: 6080
Jan 17, 2018 16:07 pm

hmmm i am not sure now.