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
Store

Average CPU clock reading 99% all the time

lpor

I am monitoring a 2012R2 windows server using NPM 11.5 and the average CPU has stuck on 99-100%

The current usage is 20-30% for the past 24 hours but I still have an active CPU alert.

Has anyone else seen this behaviour?

The server is actually the one running NPM.

I have tried tapping the clock face but its still stuck.

Find more posts tagged with

Accepted answers

silverbacksays

Since you're having the issue polling your poller from your poller, and as such there should be nothing blocking it, check if SNMP/WMI have died a death, as clubjuggle‌ suggested. Failing that, give the Orion services a bounce in your next maintenance window. Might even be worth bouncing the server while you're at it.

I expect this will have political repercussions, as polling your other nodes will stop while you refresh the services / reboot, but SolarWinds needs a break sometimes!

All comments

mharvey

What method are you using to gather the information? SNMP? WMI? Does the value change if you try poll now?

clubjuggle

LOL at tapping the clock face!

On the node details page for the node in question, look at the Polling Details section. If the time listed for "Next Poll" is in the past (by more than a minute or two) then the device has stopped responding to polling. If that's the case, you'll need to resolve the polling issue (check to see if SNMP/WMI services stopped, make sure the poller can communicate with the node, etc). Once you resolve that issue, the CPU reading should correct itself as soon as it polls again.

silverbacksays

I expect this will have political repercussions, as polling your other nodes will stop while you refresh the services / reboot, but SolarWinds needs a break sometimes!

lpor

Thanks to everyone for answers, this is what I tried --- I am using SNMP polling, the next poll time was in the past, Poll Now made no difference, restart of SNMP service made no difference but a restart of all Orion services solved the issue. I noticed that Solarwinds Collector data Processor didn't stop and had to kill the process. Restarted all services and now reading correct value.

clubjuggle

Glad you found the issue!

You may wish to update one or more of the following canned alerts to help detect this condition in the future:

Alert me when a polling engine has not updated the database in 10 minutes
Managed node Last Poll Time > 10 minutes
Managed node missed polls > 5

Note that the last two are not the exact names; I combined them into one alert in my environment, and don't remember the exact original names.

silverbacksays

Glad you got it sorted mate!

mharvey

glad you were able to clear this up. You may want to look at WMI polling on the Windows systems. I find it a bit more reliable. Also depending on the version you're on, there may be a larger issue going on that you may need to have addressed.