Network Management
High Memory Utilization for Log Viewer or Log Analyzer Trap Service
The article discusses an issue where the Polling Engine is experiencing High Memory Utilization where the SolarWinds Platform Log Trap Service is consuming it the most.
First published date
Last published date
Overview
This article describes a workaround if the LogMgmt Trap Service is consuming the Top Memory Utilization in the Polling Engine due to Trap Service was unable to translate/decode Traps with very Long untranslatable OIDs
Product section
Cause
The problem is caused by long untranslatable OIDs which causes the Trap Service to consume memory in OID Translation.
Most of the SNMP Traps cannot be translated and the Trap service just ends up wasting time trying to find them in the database, thus slowing down the processing and increasing the consumed memory.
From the Trap Service Logs, you may notice a lot of errors like this:
2024-01-10 13:16:59,997 [4] ERROR SolarWinds.Orion.LogMgmt.TrapServiceImplementation.TrapPacketProcessor - Bad trap packet received from Node with IP x.x.x.x. Error description : Error decoding. 2024-01-10 13:17:00,419 [6] ERROR SolarWinds.Orion.LogMgmt.TrapServiceImplementation.TrapPacketProcessor - Bad trap packet received from Node with IP x.x.x.x. Error description : Error decoding. 2024-01-10 13:17:00,856 [4] ERROR SolarWinds.Orion.LogMgmt.TrapServiceImplementation.TrapPacketProcessor - Bad trap packet received from Node with IP x.x.x.x. Error description : Error decoding.
From the Wireshark Capture:
Resolution
Workaround1: Disable "EnableGettingValueFromOid" Setting From Advanced Configuration Page
- Access the Advanced Configuration Settings
- Search for "EnableGettingValueFromOid"
- Uncheck it if found enabled
- Click Save
- Restart OLM Trap Service
Note: The Setting can be used if OID resolution is slow and if not resolving names is not an issue. If turned on
the resolution is completely skipped so no connection to MIB plugin is made. As a result all Varbinds are stored in the form in which they were received.
Workaround 2:
Configure the devices that send traps to the SolarWinds Platform to NOT use very long OIDs (for example: 3.6.1.4.1.12.1.0.1.1.3.6.1.4.1.26393.99.10.1.1.1.3.6.1.4.1.26393.99.10.1.2.1.3.6.1.4.1.26393.99.10.1.4.1.3.6.1.4.1.26393...).