Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > High CPU usage in SolarWinds Orion

High CPU usage in SolarWinds Orion

Updated Sep 07, 2018

Overview

This article provides brief information and steps to resolve the issue when there is high CPU utilization in Orion.

Environment

  • Orion Web Console will be unresponsive
  • Alerts will be slow
  • Gaps in Polling Data

Cause 

First, determine which process(es) are consuming the most CPU. Usually, this is the Job Engine Workers but could also any number of other processes.

 

If the Job Engine Workers are causing the issue you will need to determine which plugin jobs they are running.

 

  • Open Task Manager
  • Go to Details tab and add the "Command Line" column
  • Sort the Details tab by CPU and find the top offender(s). The Command Line will show you the plugin name

 

Another possible cause:

If you've upgraded SAM to 6.6 recently - ADM or application dependency polling is enabled across all nodes by default.

This will install the agent which is required for this feature on nodes which can cause high cpu usage when running into agent deployment failures. Also if there are connection issues with ADM plugins - it also can cause high cpu.

You can disable ADM globally following this article if you think that might be the cause of the issue:

https://support.solarwinds.com/Succe...ettings_in_SAM

 

*You'll see "nping" processes eating the cpu in task manager on the box.

Resolution

Ensure that the minimum hardware requirements are met. 

 

For 2008 R2 Servers (Windows Server 2008 R2 (no longer supported in Core 2017.3)

- There is a Microsoft Hotfix to address known WMI issues taking CPU up to 100%

(© 2013 Microsoft Corp., available at https://support.microsoft.com/en-us/kb/2505348
, obtained on June 20th, 2016.)

 

Move nodes to Additional Poller or Disable excess polling jobs 

 

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

 

Last modified

Tags

Classifications

Public