Network Management

Agent Status “Reboot Pending” Not Cleared After Agent restart and Server reboot

The “Reboot pending” status (status ID: 5) is not cleared from an agent even after rebooting the node and restarting the agent service.

First published date

9/29/2025 5:24 PM

Last published date

2/10/2026 5:35 PM

Overview

Under certain conditions, the “Reboot pending” status (status ID: 5) is not cleared from an agent.

The issue occurs when:

  • An agent reports rebootPending:true in the GetDetails message, and the Agent Management Service (AMS) stores this state in the database.

  • If AMS is restarted, and the agent subsequently reports rebootPending:false in the GetDetails message, the “Reboot pending” status is never cleared.

This results in the agent continuing to display a Reboot pending state, even though it has already reported that no reboot is required.

Product section

Orion Platform

Cause

  • An agent reports rebootPending:true in the GetDetails message, and AMS stores this state in the database.

  • If AMS is restarted, and the agent subsequently reports rebootPending:false in the GetDetails message, the “Reboot pending” status is never cleared.

Resolution

This issue is addressed in SolarWinds Platform 2026.1. Consider upgrading your environment. If you cannot upgrade, you may manually update the agent status in the database to clear the Reboot Pending status.