Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Server & Application Monitor (SAM) > JobEngine Worker Processes consume 100% CPU using 4096-keys

JobEngine Worker Processes consume 100% CPU using 4096-keys

Updated: 5-1-2017

Overview

Your JobEngine Worker Processes may consume 100% CPU when using 4096-bit keys on Linux systems using script monitors. The issue occurs due to the WeOnlyDo library in SAM 6.2.4 and later attempt to use 4096-bit keys to open SSH connections for the script monitors.

To resolve, you can open a Support ticket or use shorter keys. Longer 4096-bit keys cause issues with the WeOnlyDo library.

Environment

  • SAM 6.2.4 and later

 

Cause 

The WeOnlyDo library does not support 4096-bit keys to open SSH connections for script monitors.

Resolution

SolarWinds recommends using smaller keys, not 4096-bit keys, to open SSH connections for script monitors. You can also enter a Support ticket.

 
Last modified
13:10, 1 May 2017

Tags

Classifications

Public