Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

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