FOG Client log reporting old RC and odd behavior
-
@Joe-Schmitt No luck, still not communicating, last entry still 10/13/16. Do I need to restart the service?
-
@fry_p that’s odd that it’s not logging anything. Can you check if the service is running? If not give it a start and see if it stops itself.
-
Also see if the settings.json file inside of c:\ program files x86 \ fog is blank or not…
-
-
@Wayne-Workman It is blank. I take it that’s bad…
-
@fry_p Yeah it’s bad. We’re starting to see this bug pop up now. I was hoping it was just a fluke as I am still unsure as what’s causing it.
-
@Joe-Schmitt There seems to be no rhyme or reason to which clients this happens to. I am willing to give you any logs you need because this is becoming more and more widespread in the district. Does this explain random reboots?
-
@fry_p for the reboots if the host is truely already on the domain, it may be possible that the server is sending bad data. See my bug report here:
-
@fry_p Is there a bunch of white space inside of settings.json? Mine wasn’t just totally blank but had a bunch of spaces in it.
-
@fry_p I can push out a band-aid in a few hours that’ll prevent any more clients from loosing their settings file. We still need to find out the underlying server issue, but this patch will stop any more damage from being done.
-
@Joe-Schmitt How easy would it be to gather every GUID for every version of the new fog client?
-
@Wayne-Workman Why?
-
@fry_p This particular computer you pulled the log from in the opening post, is it configured to sleep after a specified time of inactivity? Either through settings you put on the image it uses or via GPO? If so, what is that time length set to?
-
@fry_p could you upload a copy of the blanked setting files along with a hexdump of it?
-
@Wayne-Workman @Joe-Schmitt They are configured to never go to sleep or hibernate through group policy. Give me a moment for the settings file.
-
It says I don’t have enough privileges to upload to the forums.
-
Joe Schmitt Senior Developerlast edited by Joe Schmitt Oct 31, 2016, 11:33 AM Oct 31, 2016, 5:33 PM
Odd. Could you still include the hexdump? Really that’s all I need.
-
@Joe-Schmitt not much to see, flagged it as spam when I tried to copy paste it.
-
@fry_p so that’s not good. The entire file is getting zero’d out.
-
So I’ve been thinking about lots of ways to try to detect when this happens.
The best idea I’ve had so far is to have a login script via GPO just copy each computer’s settings.json file to a share on the fog server, and have the fog server run a script every hour via CRON to do a checksum on every file, and then if any match the signature of one of the blank files, to just log it. This would give me a list of computers with the problem.
