Computer reverts to previous client and crashes.

davidedpg10 · Dec 29, 2016, 2:43 PM

Server

FOG Version: 1.3.0 REV 6050
OS: Ubuntu 14.04

Client

Service Version: 0.11.7
OS: Windows 10 Enterprise MSDN

Description

I recently upgraded Fog from rc21 to the oficial 1.3.0 release, (I was on the 0.11.5 client too). I have a computer (that I know of) that somehow it keeps getting client 0.11.5 reinstalled and it ends up with both clients, after which it crashes and restarts, and after that it does not run FOGService. Here is the last part of the log.

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 12/29/2016 8:31 AM Client-Info Client Version: 0.11.7
 12/29/2016 8:31 AM Client-Info Client OS:      Windows
 12/29/2016 8:31 AM Client-Info Server Version: 1.3.0
 12/29/2016 8:31 AM Middleware::Response Success
------------------------------------------------------------------------------

 12/29/2016 8:31 AM Service Sleeping for 91 seconds
 12/29/2016 8:31 AM Controller Stop
 12/29/2016 8:31 AM Service Stop requested
 12/29/2016 8:31 AM Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"unload\"\r\n}"
}
 12/29/2016 8:31 AM Bus Emmiting message on channel: Status
 12/29/2016 8:33 AM Main Overriding exception handling
 12/29/2016 8:33 AM Main Bootstrapping Zazzles
 12/29/2016 8:33 AM Controller Initialize
 12/29/2016 8:33 AM Zazzles Creating main thread
 12/29/2016 8:33 AM Zazzles Service construction complete
 12/29/2016 8:33 AM Controller Start

 12/29/2016 8:33 AM Service Starting service
 12/29/2016 8:33 AM Bus Became bus server
 12/29/2016 8:33 AM Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 12/29/2016 8:33 AM Bus Emmiting message on channel: Status
 12/29/2016 8:33 AM Service Invoking early JIT compilation on needed binaries

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 12/29/2016 8:33 AM Client-Info Version: 0.11.5
 12/29/2016 8:33 AM Client-Info OS:      Windows
 12/29/2016 8:33 AM Middleware::Authentication Waiting for authentication timeout to pass
 12/29/2016 8:33 AM Middleware::Communication Download: http://192.168.50.237/fog/management/other/ssl/srvpublic.crt
 12/29/2016 8:33 AM Data::RSA FOG Server CA cert found
 12/29/2016 8:33 AM Middleware::Authentication Cert OK
 12/29/2016 8:33 AM Middleware::Communication POST URL: http://192.168.50.237/fog/management/index.php?sub=requestClientInfo&authorize&newService
 12/29/2016 8:33 AM Middleware::Response Success
 12/29/2016 8:33 AM Middleware::Authentication Authenticated


 12/29/2016 8:33 AM Bus Registering ParseBus in channel Power
 12/29/2016 8:33 AM Log Unhandled exception caught
 12/29/2016 8:33 AM Log     Terminating: True
 12/29/2016 8:33 AM Log     Hash code: 13539942

Tom Elliott · Dec 29, 2016, 4:12 PM

Is there a GPO pushing out FOG Client installation?

davidedpg10 · Dec 29, 2016, 4:34 PM

@Tom-Elliott I just checked and I do not see any GPO pushing any installations.
The log does say “12/29/2016 10:18 AM Service Invoking early JIT compilation on needed binaries” which makes me think that the new client is pulling and installing the old client… I even disabled client updater supposedly, but the log seems to think I have disabled user tracker apparently.

 12/29/2016 10:16 AM Client-Info Client Version: 0.11.7
 12/29/2016 10:16 AM Client-Info Client OS:      Windows
 12/29/2016 10:16 AM Client-Info Server Version: 1.3.0
 12/29/2016 10:16 AM Middleware::Response Success
------------------------------------------------------------------------------

 12/29/2016 10:16 AM Service Sleeping for 131 seconds
 12/29/2016 10:16 AM Controller Stop
 12/29/2016 10:16 AM Service Stop requested
 12/29/2016 10:16 AM Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"unload\"\r\n}"
}
 12/29/2016 10:16 AM Bus Emmiting message on channel: Status
 12/29/2016 10:18 AM Main Overriding exception handling
 12/29/2016 10:18 AM Main Bootstrapping Zazzles
 12/29/2016 10:18 AM Controller Initialize
 12/29/2016 10:18 AM Zazzles Creating main thread
 12/29/2016 10:18 AM Zazzles Service construction complete
 12/29/2016 10:18 AM Controller Start

 12/29/2016 10:18 AM Service Starting service
 12/29/2016 10:18 AM Bus Became bus server
 12/29/2016 10:18 AM Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 12/29/2016 10:18 AM Bus Emmiting message on channel: Status
 12/29/2016 10:18 AM Service Invoking early JIT compilation on needed binaries

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 12/29/2016 10:18 AM Client-Info Version: 0.11.5
 12/29/2016 10:18 AM Client-Info OS:      Windows
 12/29/2016 10:18 AM Middleware::Authentication Waiting for authentication timeout to pass
 12/29/2016 10:18 AM Middleware::Communication Download: http://192.168.50.237/fog/management/other/ssl/srvpublic.crt
 12/29/2016 10:18 AM Data::RSA FOG Server CA cert found
 12/29/2016 10:18 AM Middleware::Authentication Cert OK
 12/29/2016 10:18 AM Middleware::Communication POST URL: http://192.168.50.237/fog/management/index.php?sub=requestClientInfo&authorize&newService
 12/29/2016 10:18 AM Middleware::Response Success
 12/29/2016 10:18 AM Middleware::Authentication Authenticated

 12/29/2016 10:18 AM Bus Registering ParseBus in channel Power
 12/29/2016 10:18 AM Log Unhandled exception caught
 12/29/2016 10:18 AM Log     Terminating: True
 12/29/2016 10:18 AM Log     Hash code: 13539942

This is the log portion about client updater and user tracker.

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 12/29/2016 10:14 AM Client-Info Client Version: 0.11.7
 12/29/2016 10:14 AM Client-Info Client OS:      Windows
 12/29/2016 10:14 AM Client-Info Server Version: 1.3.0
 12/29/2016 10:14 AM Middleware::Response Success
------------------------------------------------------------------------------

 12/29/2016 10:14 AM Service Sleeping for 104 seconds
 12/29/2016 10:16 AM Middleware::Communication URL: http://192.168.50.237/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 12/29/2016 10:16 AM Middleware::Response Success
 12/29/2016 10:16 AM Service ERROR: Invalid promptTime, using default
 12/29/2016 10:16 AM Middleware::Communication Download: http://192.168.50.237/fog/management/other/banner.jpg
 12/29/2016 10:16 AM Middleware::Communication URL: http://192.168.50.237/fog/management/index.php?sub=requestClientInfo&mac=F4:CE:46:2D:DE:7F||00:00:00:00:00:00:00:E0&newService&json
 12/29/2016 10:16 AM Middleware::Response Success
 12/29/2016 10:16 AM Middleware::Communication URL: http://192.168.50.237/fog/service/getversion.php?clientver&newService&json
 12/29/2016 10:16 AM Middleware::Communication URL: http://192.168.50.237/fog/service/getversion.php?newService&json

 12/29/2016 10:16 AM Service Creating user agent cache
 12/29/2016 10:16 AM Middleware::Response Success
 12/29/2016 10:16 AM Middleware::Response Module is disabled globally on the FOG server
 12/29/2016 10:16 AM Middleware::Response Module is disabled globally on the FOG server

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 12/29/2016 10:16 AM Client-Info Client Version: 0.11.7
 12/29/2016 10:16 AM Client-Info Client OS:      Windows
 12/29/2016 10:16 AM Client-Info Server Version: 1.3.0
 12/29/2016 10:16 AM Middleware::Response Success
------------------------------------------------------------------------------

Joe Schmitt · Dec 29, 2016, 5:20 PM

@davidedpg10 according to those logs user tracker is working properly and client updated is disabled. (User tracker only logs something when a login or logout event is detected). And client updated will only log something when an update is needed (and client updated is enabled).

As for the JIT message, that happens on every client startup to speed up things like the shutdown prompt’s response time. It does not install the old version of the client.

Could I get the full fog log from this computer? And could you double check on GPO? Generally whenever we see this issue there is a client policy somewhere.

davidedpg10 · Dec 29, 2016, 6:49 PM

@Joe-Schmitt
I will recheck the GPO, the log file got pretty big as the issue has been happening around every 3 hours. I have also checked SCCM deployments and nothing seems to be scheduled. I have embedded the log. Thank you guys for helping.0_1483037359489_fog.log

Wayne Workman · Jan 4, 2017, 5:31 PM

@davidedpg10 In fog, set that problematic host to not join the domain, and then take that host off of the domain manually. See if the old version problem persists or not, to be through give it a reboot every 1 - 3 hours, log in each time and check.

Check logs, check the services, check the tray, check windows event logs. Because we don’t know what the issue is, you need to be extra observant.

If it still happens, uninstall the SCCM client and then give it another go.

Something is reinstalling the old client, you just have to figure out a way to isolate what is doing it.

davidedpg10 · Jan 4, 2017, 5:31 PM

@Wayne-Workman My apologies, it was in fact an SCCM Deployment. I did not fully understand how SCCM deployments worked, I did not realize that once set, it will check periodically if it is still compliant with said deployment. It’s not a one time deal.

Tom Elliott · Jan 4, 2017, 5:34 PM

@davidedpg10 So this is now working? (AFter fixing the task sequences)?

davidedpg10 · Jan 4, 2017, 5:34 PM

@Tom-Elliott yes it is, Please mark this thread as solved, and thank you for your help.

Computer reverts to previous client and crashes.

Server

Client

Description

183

12.1k

17.3k

155.3k