Client shutdown (Service manager shutdown request)

Usage and Config Platform
1

(imported topic written by MattBoyd)

While running a fairly long action I noticed that the BigFix client service seems to randomly restart on clients. When this occurs, my action fails, regardless of what the outcome actually was. I don’t think that the service restarts because of the action, because I’m seeing this in the logs in a lot of machines where the action wasn’t executed. Are there any common causes for this?

Here’s a log excerpt from a client with a random restart that seems to happen once a day:

…
At 00:25:49 -0400 -
Report posted successfully.
At 00:48:12 -0400 -
Report posted successfully.
At 01:10:47 -0400 -
Report posted successfully.
At 01:11:06 -0400 -
Client shutdown (Service manager shutdown request)
At 01:12:06 -0400 -
Starting client version 7.2.4.60
At 01:12:07 -0400 -
FIPS mode disabled by default.
At 01:12:08 -0400 -
Restricted mode
…

Log from another day on the same client

…
At 00:02:06 -0400 -
Report posted successfully.
At 00:24:44 -0400 -
Report posted successfully.
At 00:47:07 -0400 -
Report posted successfully.
At 01:09:30 -0400 -
Report posted successfully.
At 01:15:06 -0400 -
Client shutdown (Service manager shutdown request)
At 01:16:05 -0400 -
Starting client version 7.2.4.60
At 01:16:06 -0400 -
FIPS mode disabled by default.
At 01:16:07 -0400 -
Restricted mode
At 01:16:12 -0400 -
…

And on the same client from another day…

…
At 02:08:07 -0400 - opsite9 (http://:52311/cgi-bin/bfgather.exe/opsite9)
Successful Synchronization with FixSite (version 67) - 'http://:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://:52311/cgi-bin/bfgather.exe/opsite9’
At 02:13:31 -0400 -
Client shutdown (Service manager shutdown request)
At 02:14:33 -0400 -
Starting client version 7.2.4.60
At 02:14:34 -0400 -
FIPS mode disabled by default.
At 02:14:36 -0400 -
Restricted mode
…

2

(imported comment written by SystemAdmin)

The (Service manager shutdown request) means that something stopped the BES Client service and restarted it.

It is possible that a BigFix action ran and caused the shutdown but I don’t see any indication of that in the logs. The BES Client doesn’t shut itself down like this on it’s own, it would only do so through an action running.

It’s possible the action ran along time ago and included a restart command which didn’t get kicked off until this point in time. I think this is most likely because the client doesn’t start again for 1 minute, which is enough time for the computer to reboot.

Some actions require restarts before the final action status is known. The restarts should affect the final status, it is more likely that your action is just failing and you just don’t get the ‘failed’ status until the computer is restarted.

Actions will be ‘failed’ if the Fixlet is still relevant after the action runs.