N-central Troubleshooting
Device didn't reboot during Maintenance Window
Last Modified
Sat Oct 24 06:53 GMT 2020
Description
- A Maintenance Window is configured to reboot the device, but it did not reboot.
Environment
- N-able N-central 9 or later
Solution
A scheduled reboot will not proceed if there is any active msiexec.exe process running.
- Check the type of the Maintenance Window under the Type column to see if it was a Patch Reboot or a Scheduled Reboot type.
- Patch Reboot will only execute a reboot if and only if the device has had a patch installed by N-able N-central Patch Management, requiring a reboot.
- Patch Reboot will not execute if there is any other type of pending reboot, even if it was a manual patch install or 3rd party software install requiring reboot, as potentially seen on the Reboot Status service.
- If the Reboot window is configured to Force User to Reboot, and the prompt and countdown for is longer than maintenance window should last for value, the device will not reboot if any users are still logged in.
Example evidence:
Scheduled Reboot - 2019-01-22 16h02m00s
Prompt and Countdown For: 60
Maintenance window should last for: 30
[183] 2020-10-20 22:15:28,072 WARN com.nable.agent.Reboot.RebootManager **** NOTE: Force Reboot will be request for this Maintenance Schedule with Name: Scheduled Reboot - 2019-01-22 16h02m00s ID: 1210749665
[200] 2020-10-20 22:44:28,386 WARN com.nable.agent.Reboot.RebootManager **** NOTE: Force Reboot will be request for this Maintenance Schedule with Name: Scheduled Reboot - 2019-01-22 16h02m00s ID: 1210749665
[183] 2020-10-20 22:45:28,405 WARN com.nable.agent.Reboot.RebootManager Clearing temp reboot request values for schedule with Name: [ Scheduled Reboot - 2019-01-22 16h02m00s ] ID: [ 1210749665 ]
[183] 2020-10-20 22:45:28,405 <<*>> com.nable.agent.Reboot.RebootManager Schedule [ Scheduled Reboot - 2019-01-22 16h02m00s ]: Current time is not in reboot window.