@FredG I’ve added more implicit checking to the working branch to prevent this type of error.

For what it’s worth, I’ve added checking for the variables so this shouldn’t be an issue anymore.

@Tom-Elliott

Hi tom That fixed the problem, Thanks for all your help!!

@Tom-Elliott

Hi Tom,

according to the client log file it says " snapinclient module is disabled globally on the FOG Server, exiting."

I will create a new issue, and post the log file from one of the clients.

Thanks!

I cannot replicate, but that doesn’t mean much. I’m running the working branch.

Mind giving the working branch a shot and seeing if the issue still exists?

Ok.
thank you for the work done.

A very simple question, I suppose, but do the hosts that are registering have the new or legacy client?
Can you provide the client log of one of the “adding” systems? (If you are using legacy client please post one for each of the clients – one legacy client fog.log and one new client)

Oups my bad, just saw this thread https://forums.fogproject.org/topic/9399/client-doesn-t-seem-to-auto-update-stuck-in-a-loop-of-updating
It’s ok now !

Please run:

cd fogproject #if you're not in the git folder already. rm binaries1.3.4.zip cd bin ./installfog.sh

Forgot to update binaries.zip with the 0.11.9 files sorry about that.

@Tom-Elliott
Hi Tom, just wanted to make you aware whatever changes were made recently in regards to additional mac addresses have fixed this issue now in 1.3.4-RC-2 thank you.

I suspect the reasoning it “hangs” waiting for input unless only one option is defined is the timeout -1.

@Tom-Elliott I didn’t see it mentioned in the release notes hence the post. I’ll update.

@Tom-Elliott
Thanks for the quick fix. PXE-Boot is working again now! You are not only a good developer but also rocket-fast 😉

https://news.fogproject.org/fog-1-3-4-rc-1/

https://news.fogproject.org/fog-1-3-4-rc-1/

Thanks to Tom’s speedy remote work the problem was found and fixed with the release of 1.3.3.

Thanks for reporting back.

@george1421 Thanks, I will.

Fixed for the working 1.3.3 branch.

@Tom-Elliott

Just here to thank you for this!