nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

CPU sticking at 100 Percent Utilization

drbaltz

I've got Orion 8.1 installed and on one of my servers, it shows that the CPU utilization is at 100 percent 24/7. When I check the server, it is averaging around 1% utilization and never goes to 100%. Any ideas on how to fix this issue?

Find more posts tagged with

100%_cpu

Accepted answers

All comments

mark_wiggans

As a suggested workaround you can try deleting the CPU as a resource
for the node and then re-adding it, however I would also encourage you to submit a ticket so support can provide further analysis. What type of device is this?

jds

Yeah I'd second the question about what device ths is. I've seen Linux/Unix systems have CPU util being reported wrong. But that is the nature of SNMP and Linux. In fact all my Linux systems are constantly at 34% util reported through SNMP. Now if SolarWinds could fix that...

mark_wiggans

jds-

If you're using
Net-SNMP, try upgrading to the latest version or reinstalling/uninstalling it-

drbaltz

Sorry, this is a Compaq Proliant DL380 running Windows Server 2003. I have the same problem on Mac OS X Server. Doesn't matter what version of net-snmp I use, as soon as I start the service and monitor it with Orion, the CPU spikes to 100% on the Mac server. Haven't found a fix yet and this has been an issue with Solarwinds for quite sometime now. Surprised there is not a fix yet.

FYI, deleting the node from Orion and then re-adding it fixed the issue.

jamesbernhard

With no changes to my environment on the polled node side or poller I am now seeing this as well. I have 5 windows 2003 servers that are constantly reporting 100% cpu utlization. During this reported period they are not being utilized at all. I run 8.1 w/ only hotfix 1 and 2 installed. I have removed the cpu resource and added it back. I have restarted snmp on the polled node side. Nada still, killing me b/c of capacity planning reports now aren't accurate. I have another ~800 servers not experiencing this issue.

WINNT

I have the same issue with the CPU counter sticking. It happens on Windows, and various flavors of Unix. I have even seen it stick on a Windows cluster name, but not on the nodes. I just have to remove the CPU monitor and then add it again. I too am surprised that this hasn't been addressed by SolarWinds.

mark_wiggans

I too am surprised that this hasn't been addressed by SolarWinds.

We are aware of this issue and it will be addressed shortly after the 8.5 release-

Below are some of the suggested workarounds which may help:

Try switching the device from SNMP v2 to SNMP v1 and attempting to poll again. It may simply be that is cannot respond to the version of SNMP that is hitting the device-

Other suggestions to try:
1) Right-click on the node and choose "List Resources". Uncheck the CPU utilization. Click Okay, then right click on the node and choose "Poll now". Then list resources again, check CPU utilization, and click okay. Then choose "Poll Now" again.
If that does not clear it-

2) Try adding the node again - do not delete the existing node, simply click on New and enter in the same credentials.

drbaltz

None of those workarounds worked for our Mac OS X Server boxes.

Are you guys going to fix the hard drive monitoring issue in Orion for Mac OS X too? This is when you click to monitor an OS X mounted HDD in Orion and it spikes the CPU on the monitor Mac OS X system to 100% CPU usage until you kill snmpd. This has been going on for as long as I can remember.

anselm

check your version of net-snmp that you are using-

docs.info.apple.com/article.html

WINNT

You can also restart the NetPerfMon service to unstick the CPU monitor.

drbaltz

Just FYI everyone. Orion 8.5 didn't fix anything with monitoring Mac OS X. CPU and memory still read 100% and if you monitor volumes the xserve's CPU utilization goes up to 100% and you have to manually kill the snmpd service. I've verified this on net-snmp 5.3.1 (version that is supposed to work) and on 5.4.1.

Can we please get this working Solarwinds? This has never worked correctly! People do want to monitor Macs too...

FormerMember

We are actively working on it. We have finally been able to reproduce in-house, and so we think we know the source of the problem at this point. We are going to deliver it as a hotfix on top of 8.5..

chris.conway

Hotfix doesn't appear to have fixed it.... at least not for my customer.

Support ticket is 10600