FOG Service and interventions

[sgoodman]

Fog Version 1.5.7.49
Windows 10 Enterprise version 1903
FOG Client version v0.11.16
Installed using “Smart Installer”
Client installed as a component of the image (before the image capture)
Yes followed all Sysprep instructions.

Tail end of fog.log below:

---

--------------------------------PowerManagement-------------------------------

11/7/2019 10:39 AM Client-Info Client Version: 0.11.16
11/7/2019 10:39 AM Client-Info Client OS: Windows
11/7/2019 10:39 AM Client-Info Server Version: 1.5.7.49
11/7/2019 10:39 AM Middleware::Response Module is disabled globally on the FOG server

---

----------------------------------UserTracker---------------------------------

11/7/2019 10:39 AM Client-Info Client Version: 0.11.16
11/7/2019 10:39 AM Client-Info Client OS: Windows
11/7/2019 10:39 AM Client-Info Server Version: 1.5.7.49
11/7/2019 10:39 AM Middleware::Response Success

11/7/2019 10:39 AM Service Sleeping for 101 seconds
11/7/2019 10:40 AM Middleware::Communication URL: http://fog.mscs.mu.edu/fog/management/index.php?sub=requestClientInfo&configure&newService&json
11/7/2019 10:40 AM Middleware::Response Success
11/7/2019 10:40 AM Middleware::Communication URL: http://fog.mscs.mu.edu/fog/management/index.php?sub=requestClientInfo&mac=3C:52:82:76:63:BB|00:50:56:C0:00:01|00:50:56:C0:00:08|02:50:41:00:00:01&newService&json
11/7/2019 10:40 AM Middleware::Response Success
11/7/2019 10:40 AM Middleware::Communication URL: http://fog.mscs.mu.edu/fog/service/getversion.php?clientver&newService&json
11/7/2019 10:40 AM Middleware::Communication URL: http://fog.mscs.mu.edu/fog/service/getversion.php?newService&json

11/7/2019 10:40 AM Service Creating user agent cache
11/7/2019 10:40 AM Middleware::Response Success
11/7/2019 10:40 AM Middleware::Response Success
11/7/2019 10:40 AM Middleware::Response Module is disabled globally on the FOG server

---

---------------------------------ClientUpdater--------------------------------

11/7/2019 10:40 AM Client-Info Client Version: 0.11.16
11/7/2019 10:40 AM Client-Info Client OS: Windows
11/7/2019 10:40 AM Client-Info Server Version: 1.5.7.49
11/7/2019 10:40 AM Middleware::Response Success

---

----------------------------------TaskReboot----------------------------------

11/7/2019 10:40 AM Client-Info Client Version: 0.11.16
11/7/2019 10:40 AM Client-Info Client OS: Windows
11/7/2019 10:40 AM Client-Info Server Version: 1.5.7.49
11/7/2019 10:40 AM Middleware::Response Success

---

--------------------------------HostnameChanger-------------------------------

11/7/2019 10:40 AM Client-Info Client Version: 0.11.16
11/7/2019 10:40 AM Client-Info Client OS: Windows
11/7/2019 10:40 AM Client-Info Server Version: 1.5.7.49
11/7/2019 10:40 AM Middleware::Response Success
11/7/2019 10:40 AM HostnameChanger Checking Hostname
11/7/2019 10:40 AM HostnameChanger Hostname is correct
11/7/2019 10:40 AM HostnameChanger Attempting to join domain
11/7/2019 10:40 AM HostnameChanger Host already joined to target domain

---

---------------------------------SnapinClient---------------------------------

11/7/2019 10:40 AM Client-Info Client Version: 0.11.16
11/7/2019 10:40 AM Client-Info Client OS: Windows
11/7/2019 10:40 AM Client-Info Server Version: 1.5.7.49
11/7/2019 10:40 AM Middleware::Response No snapins

---

--------------------------------PrinterManager--------------------------------

11/7/2019 10:40 AM Client-Info Client Version: 0.11.16
11/7/2019 10:40 AM Client-Info Client OS: Windows
11/7/2019 10:40 AM Client-Info Server Version: 1.5.7.49
11/7/2019 10:40 AM Middleware::Response Success
11/7/2019 10:40 AM PrinterManager Adding printers
11/7/2019 10:40 AM PrinterManager CU101 Printer already exists
11/7/2019 10:40 AM PrinterManager CU145 Printer already exists
11/7/2019 10:40 AM PrinterManager CU201 Printer already exists
11/7/2019 10:40 AM PrinterManager CU240 Printer already exists
11/7/2019 10:40 AM PrinterManager CU301 East Printer already exists
11/7/2019 10:40 AM PrinterManager CU310 Printer already exists
11/7/2019 10:41 AM PrinterManager CU336 Printer already exists
11/7/2019 10:41 AM PrinterManager CU340 Printer already exists
11/7/2019 10:41 AM PrinterManager CU357 Printer already exists
11/7/2019 10:41 AM PrinterManager CU395 Printer already exists
11/7/2019 10:41 AM PrinterManager CU410 Printer already exists
11/7/2019 10:41 AM PrinterManager CU412 Printer already exists
11/7/2019 10:41 AM PrinterManager CU417 Printer already exists
11/7/2019 10:41 AM PrinterManager CU421 Printer already exists

---

--------------------------------PowerManagement-------------------------------

11/7/2019 10:41 AM Client-Info Client Version: 0.11.16
11/7/2019 10:41 AM Client-Info Client OS: Windows
11/7/2019 10:41 AM Client-Info Server Version: 1.5.7.49
11/7/2019 10:41 AM Middleware::Response Module is disabled globally on the FOG server

---

----------------------------------UserTracker---------------------------------

11/7/2019 10:41 AM Client-Info Client Version: 0.11.16
11/7/2019 10:41 AM Client-Info Client OS: Windows
11/7/2019 10:41 AM Client-Info Server Version: 1.5.7.49
11/7/2019 10:41 AM Middleware::Response Success

11/7/2019 10:41 AM Service Sleeping for 137 seconds

[Daniel Miller]

No logged errors… do you see any warnings or errors in the System or Applications logs at or around the time that the last log entry happens? On a machine with a crashed service, what do sc query fogservice and sc qc fogservice return?

[sgoodman]

@Daniel-Miller Nope, once FOG Service stopped, it discontinued any logging. On the windows log side can’t find a thing. sc query and sc qc all look good as it is running now.

I get no indication that service crashed - basically something didn’t work (fog based printer creation for example) then I manually look around and need to restart the service (and printer gets created).

I’ve also noticed that if I am creating a lot of printers on a host (10 or more let’s say) it gets partially through then dies. I start up FOGService again and it completes.

Wish I had more data to go through.

[Daniel Miller]

You may have to enable auditing for the fog service. That will at least tell you if Windows thinks that the service stopped. The steps for doing so are here (sorry I don’t have a more authoritative link).

sc query fogserviceshould give the exit code of the executable when run on a machine with a crashed service.

[george1421]

@Daniel-Miller I remember reading a post not to long ago involving Win10 and 1903 where the fog service would just stop running on the target computer, whereas there was no problem with earlier versions of Win10 (the last OS you will ever need…).

@Developers Wasn’t the FOG client patched to fix this issue? I can’t seem to find the thread at the moment with the solution. I think zazzle something was involved.

[sgoodman]

@george1421 I heard the same information. A windows update caused FOGService issues. I have not seen a new Fog Client however.

[Daniel Miller]

hmm, must have missed that one. Last commit I see on zazzles was for some library updates. Don’t see any specific references to service stops on 1903 in the commit notes , but could be related. Don’t see any commit notes regarding service stops on fog-service either.

Were you thinking of https://forums.fogproject.org/topic/13704/fog-service-quits-running ?

[george1421]

@Daniel-Miller Yes that was the post I couldn’t seem to find. I thought there was some background work done on it too and an updated version of the fog client was created. But frankly, I read too many posts as it is and I think I’ve mixed up some in my gray matter.

[Sebastian Roth]

@Daniel-Miller Great you guy found that topic. That’s exactly what I’d guess is happening in @sgoodman’s case too. @george1421 Unfortunately I have not worked on this issue yet but I plan to do so over the next weeks. As we seem to have more and more reports of this issue I might need to push up the priority of this as well.

[Sebastian Roth]

@sgoodman I just finished some testing and I can’t replicate the fog-client crash yet. So far I guess it’s either related to particular updates (I had some .NET updates as well as system updates) or caused by some particular GPO WSUS settings (just a wild guess). Here is a picture of the update test with the fog-client running all the way through without a single crash - watching the log file (powershell get-contents -wait and the services view):

[Sebastian Roth]

@Daniel-Miller @george1421 @sgoodman Anyone an idea? How are we going to find what is causing this if I can’t replicate the problem?!

[Daniel Miller]

@Sebastian-Roth without logs, dumps, or the ability to replicate, options for doing so are getting kinda thin…

[Greg Plamondon]

@sgoodman Is the server set to Delayed auto?

[Sebastian Roth]

@sgoodman @Daniel-Miller @Greg-Plamondon @george1421 Has anyone run into this issue (again)? I’d think this might have been caused by a major .NET framework update which we can’t do much about.

In case people have PCs running for a long time without restart they might consider setting the service to auto-restart.

I am marking this solved now. Feel free to post if you think it’s not.

Cross reference to another topic: https://forums.fogproject.org/topic/13704/fog-service-quits-running