Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

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

Tags

Classifications

Public