Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > 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