FOG service on 0.10.6 not restarting after reboot

[tmerrick]

I seem to be seeing a race condition on the FOG service on Windows 10 where the startup fails after windows starts. My server is at 7647 and the client FOG service runs okay after I start it up via the services panel. Just to test it out I added an automatic restart on the service after it fails and this starts it up after a reboot. Is it dependent on the Task Scheduler service?

[Wayne Workman]

Alerting @jbob to this.

[Joe Schmitt]

I need more information. Is there a fog.log? Can you start it manually (get the fog.log first before trying this)?

[tmerrick]

That is how I detected that the service was not running. The fog.log stays at the last time stamp and never updates. So there are no entries there. But the event log has:

FOGService service failed to restart due to the following error: The service did not respond to the start or control request in a timely fashion.

[tmerrick]

I found two more entries in the Event Log. Here are all 3:

Task Scheduler service found a misconfiguration in the NT TASK\FOG\0@23@s definition. Additional Data: Error Value: C:\Program Files (x86)\FOGPower.exe.

The FOGService service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion

A timeout was reached (30000 milliseconds) while waiting for the FOGService service to connect.

The first one is keeping GreenFog from working. The last one (first in time order) was why the FOGService failed. This should either have a much longer timeout or dependency as it is taking Windows 10 too long to initialize things.

[Joe Schmitt]

Again, I need to see the fog.log

[tmerrick]

There is nothing in the FOG log after the reboot. The job is failing before it writes to it. Did you want the log before the reboot?

[Joe Schmitt]

Please check the FOG service installation directory for a zazzles.log

[tmerrick]

“c:\Program Files (x86)\FOG” does not have a zazzles log file in it. It only has the .dll and .xml files in it.

[x23piracy]

Hi,

have you tried to alter the service startup from automatic to delayed?
Is this a client install after (sysprep, deployment) or a fixed test machine to play around with fog client?

Regards X23

[Joe Schmitt]

Issue confirmed but the source of it is still unknown. I need more data / machines to collect info from. @Testers @Developers @Moderators has anyone seen this issues on your machines?

[tmerrick]

X23 - yes the delayed start does seem to work in the few cases that I have tried so far. Also, this is Windows 10 Enterprise on older physical machines with only 4 GB memory.

[JJ Fullmer]

@tmerrick
A few troubleshooting questions…

• Have you tried a fresh install of the service. As in uninstalling from the Programs and Features control panel and then deleting the program files folder. Then installing a fresh fog client and installing it that way?

• Is this a clean/fresh install of windows or a customized image that you are updating the fog client on?

• Was the windows installer image/disk/dism/wim customized in some way?

• If this is a customized image, what programs or at least types of programs have you added and do any of them have services that start at startup?

• Can you login with an admin user and or standard user (local or domain) and add a .log file to the root of the C drive manually?

• Is your image created from a VM or a physical machine?

@jbob Some more data. I have many older machines running windows 10 x64 enterprise with the fog client working fine. Some with less only 2 GB of memory. I even have 32 bit windows 10 enterprise with the fog client working on a pentium 4 computer with 1 gb of ram. If it is a problem with the age of the machines, perhaps they have amd cpus? I did run into some weird problems with some of our programs not working when putting windows 10 on a AMD vision laptop. Nothing wrong with the fog client that I saw, it was a different program and we had to put it back to windows 7. So @tmerrick What are the specs of the troublesome machines?

[tmerrick]

I already tried to uninstall/reinstall the service to no avail. It was a clean install of windows, but now is very customized with CAD and other programs. The physical boxes are Dell Optiplex 960-990 intel i5 computers where the image was also created.

[Tom Elliott]

@tmerrick Is it likely there’s an application causing a hangup on the startup of a dependency that FOG CLient is trying to use and cannot gain access to until far later?

Did this occur before all the “custom software?”

[tmerrick]

I installed it fresh on a client without all of the CAD programs and it worked. So it is not a 10 Enterprise problem.

I then did a fresh install on the client - Deleting the FOG program folder and re-installing (and resetting the Encryption key). And this also has worked.

I have updated the server copy and I am sysprepping right now. I will let you know the results in about an hour.

[JJ Fullmer]

@tmerrick
@Tom-Elliott said in FOG service on 0.10.6 not restarting after reboot:

@tmerrick Is it likely there’s an application causing a hangup on the startup of a dependency that FOG CLient is trying to use and cannot gain access to until far later?

Did this occur before all the “custom software?”

CAD software typically also includes licensing services. It is possible that one of them is causing trouble.
I have one optiplex 790. So I’ll do some checking on that computer to see if perhaps this is happening and I missed something.

[JJ Fullmer]

@Arrowhead-IT said in FOG service on 0.10.6 not restarting after reboot:

I have one optiplex 790. So I’ll do some checking on that computer to see if perhaps this is happening and I missed something.

Well poo. Mine is doing the same thing…
@Jbob

I checked it and the fog service was stopped. Which it did mid-update from .9.12 to .10.5. I started it and then after a couple minutes it updated itself to .10.6. Gave it a reboot and the service did not start. Checking this one another computer I’m testing. An Intel Computer Stick that I did a fresh install of windows 10 32 bit enterprise. The fog client is already on it and joined it to the domain. Checking that to see if I can isolate the issue.

[JJ Fullmer]

On the fresh install of windows 10 32 bit LTSB it works perfectly fine.

The other computer is a CB image, is it possible that this is a problem from a recent windows 10 update?

[tmerrick]

Mine definitely fails during the imaging process. The delayed start seems to make it work, but this is not a fix.

The image is definitely up to date and may have the dreaded 1511 upgrade installed. I have not been able to tell if it does or not. It is not showing up under windows updates.