Already a NinjaOne customer? Log in to view more guides and the latest updates.

NinjaOne NMS: Troubleshooting: High CPU Usage For The NMSManager.exe Process

Topic

This article provides a solution if you are experiencing high CPU usage for the NMSManager.exe process.

Environment

NinjaOne Network Management System (NMS)

Prerequisites

NMS Delegate hardware requirements: 

An advanced network adapter is recommended for network monitoring and is required for more extensive networks. 
 CPU CoresMemory (GB)NICDisk Space (GB)
Monitored Devices (#)
1–2048100BASE-T12
21–506121000BASE-T20
51–1008161000BASE-T25
Options
Netflow/SFlow+50%+50% +100%

 

Solution

  1. Check for the following common issues: 
    • Syslog, traps, or NetFlow traffic that may be thrashing the endpoint. 
    • Debug logging may need to be deactivated or turned off. 
    • Use Process Explorer to see if there are threads consuming CPU cycles. 
  2. If the issues above were not the source of the problem, gather extended logs and send them as zip files to NinjaOne Support for resolution.

If you need help gathering the logs, please refer to the process below: 

Collect Logs

  1. Open the endpoint's control panel to edit the system environment variables. You can easily find this by typing "environment" into your system's search tool and selecting the control panel option. 
    The System Properties modal displays.

edit system variables.png
Figure 1: Edit the system environment variables

  1. Click Environment Variables under the Advanced tab. 

system properties_environment variables.png
Figure 2: System properties → Advanced → Environment variables

  1. Under System variables, click New. 
    The New System Variable configuration modal displays. 

edit system variables_new.png
Figure 3: System properties → Advanced → Environment variables → New system variable

  1. Enter "NJ_Debug" into the Variable name field. Enter "1" into the Variable value field.

new variable.png
Figure 4: Create new system variable

  1. Stop the following services: 
    • NinjaRMMAgent
    • NinjaOne NMS Manager
  2. Start the NinjaRMM service. This will also start the NinjaOne NMS Manager Service.
  3. Wait about 15 minutes while the logs are created. 
  4. Create zip files for the following: 
    • %systemdrive%ProgramDataNinjaRMMAgentnmsjsoninput
    • %systemdrive%ProgramDataNinjaRMMAgentnmslogs
  5. Remove the environment variables and stop the NinjaRMM agent and the NMS manager service. 
  6. Re-start the NinjaRMM service.
  7. Send the zip files created in Step 8 to NinjaOne Support for resolution. 

 

FAQ

Next Steps