Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Last Reboot Time Updated Incorrectly

I restarted one of my APE and the reboot event was created for the correct timezone. Later, I saw that there was one more reboot event triggered(it was the last month's reboot time) with incorrect time. The Server reflected the SystemUptime value correctly , Still Orion didn't poll the right information.

I tried restarting the services and running the config wizard but there was no update on the last reboot time.
I tried removing the old ShadowCopyCache files but that didn't help as well.

CPU,Memory, Volume Pollers on the APE was functioning correctly but the last reboot time got the issue. Any idea on how to resolve this?

Find more posts tagged with

Accepted answers

All comments

Seashore

Two things to now about the time of reboot:

The timezone of all orion-servers, incl SQL, must be the same
The reboot time is that of the snmp-service and not the node, if polling with snmp

aksh14

Hi,

Main Orion, APE and DB servers time were in Sync and the node was polling with WMI.

I restarted the Server and this time the reboot event was triggered with the Correct time.