and from bigfix logs (/var/opt/BESClient/__BESData/__Global/Logs/):
At 00:03:04 -0400 - BES Support (http://sync.bigfix.com/cgi-bin/bfgather/bessupport)
Relevant - Restart Needed (fixlet:177)
At 00:03:13 -0400 -
IBM BigFix Restart (Force count:2) from ActionID 2119694
Exiting restart only state; no restart pending
At 00:03:14 -0400 -
Report posted successfully
IBM BigFix Restart from ActionID 2119694
Exiting restart only state; no restart pending
At 00:03:15 -0400 -
Report posted successfully
At 00:03:16 -0400 -
IBM BigFix Restart from ActionID 2119694
Exiting restart only state; no restart pending
At 00:03:18 -0400 -
IBM BigFix Restart from ActionID 2119694
It’s sending the system reboot command multiple times because the reboot isn’t happening and it is retrying the command (unless your machine is able to reboot in less than a second - those commands are time-stamped at the same second). Is something blocking the reboot command?
I just checked other servers and this seems to happen most of the times even on servers were patching completes successfully, however I checked /var/log/messages and it seems the server only booted ounce despite the multiple reboot commands sent by BigFix.
The log may show multiple requests to reboot as we keep issuing it to try and get the system to restart. There can be applications that can abort a restart or take a long time to shut down.