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 > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > High CPU load in SolarWinds NPM service

High CPU load in SolarWinds NPM service

Created by Karen Valdellon_ret, last modified by Aileen de Lara_ret on Oct 05, 2016

Views: 6,570 Votes: 0 Revisions: 3

Overview

This article provides brief information and steps to resolve the issue when NPM has high CPU load condition.

Environment

All NPM versions

 

Cause 

Many applications, including Access databases, like MIBs.cfg, may be configured to temporarily store files in the Windows temp directory. If these temporary files are not deleted when they are no longer needed and the number of these files in the Windows temp directory reaches 64k, the SolarWinds Network Performance Monitor Service can no longer write the temp files it requires. When this happens, the SolarWinds Network Performance Monitor Service will enter a loop where it tries to create a file that it cannot store anywhere, ultimately consuming up to 100% CPU load.

Resolution

Delete all files from the Windows temp directory on your Orion Server.

 

Last modified

Tags

Classifications

Public