The FOGScheduler logs just show my 7 scheduled cron wake up jobs. I have disabled all of the FOG services and they still started up. Thus it does not appear to be FOG. I am trying to get a hold of a network analyzer to trace who is really sending this signal. Thanks for your help in understanding how FOG works, it has helped me narrow down who is causing the problem.

I know it is a WOL being sent as my boot is SSD, then IP/PXE and it is PXE booting. Also, it is only happening in one of my three buildings. And only about 1/3 to 1/2 of the computers that I have in that building. So it looks like I have a rogue server somewhere in that building.

Just to help clarify, basically it was filtering the array out. Because there was only two tasks, and one of them was invalid, it was not defining the tasks as an array.

@tmerrick client log before it’s deleted, please.

Confirm that it works in GIT 8259.

@tmerrick I know this is asking a bit much, but if you swap one of the class 10 or class 20 with a samsung evo’s do they exit correctly with San boot? That would help us identify that it is clearly something different with these class 10+ drives or the motherboard. If you don’t have time to debug that is ok. It would just help the next guy with the same issue.

I’m going to mark this thread as solved either way. Thanks again for your feedback.

@Tom-Elliott all good now, problem solved.

Regards X23

Confirmed that it works in 8064.

Bug confirmed, the culprit? There was a + typed in the code instead of a ,
https://github.com/FOGProject/fog-client/blob/master/Modules/GreenFOG/Windows/WindowsGreen.cs#L50

This will be patched in the next version.

@tmerrick I’m making an implicit check for the interface based on the ip stored for the node.

Can you just run update.

@gwhitfield said in FOG service on 0.10.6 not restarting after reboot:

demon ninja gremlins

We are certified demon ninja gremlin dispatchers.

It already does this.

Here is part of the access log for each computer and it happens every minute, not 5 minutes that I thought that I had set above.
access_log.txt

4258 should fix this.

Invalid security token is your problem here please go to host management find this relevant post and select reset encryption data they should correct your problem

version 4238 should fix the typo.

Correct.

Its an issue with the beta client which is fixed in my v0.9.0 nightly builds.

3642 fixes this.

Works okay in fog version 3642