Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > Log & Event Manager (LEM) > LEM Memory Low - Millions of Alerts waiting

LEM Memory Low - Millions of Alerts waiting

Created by Craig O’ Neill, last modified by Mindy.Kerber on Oct 19, 2016

Views: 880 Votes: 0 Revisions: 3

Overview

In cmc → appliance → diskusage you see Millions of Alerts waiting in Memory

Symptoms of a Memory leak in LEM

Agents not reporting to LEM

Environment

  • LEM 6.1

 

Cause 

The addition of the isThreat field in the 6.2.0 agents are making the events incompatible with the 6.1.0 manager.

 

Results in the following exception

 

java.lang.ArrayIndexOutOfBoundsException: 10
at com.solarwinds.lem.database.lucius.LuciusDataWriter.writeBufferToLucius(LuciusDataWriter.java:609) [lem_lucius.jar:6.1.0.448.474828]
at com.solarwinds.lem.database.lucius.LuciusDataWriter.writeBufferToLucius(LuciusDataWriter.java:298) [lem_lucius.jar:6.1.0.448.474828]
at com.solarwinds.lem.database.lucius.LuciusAlertStorage.postBufferData(LuciusAlertStorage.java:76) [lem_lucius.jar:6.1.0.448.474828]
at com.solarwinds.lem.database.lucius.LuciusAlertStorage.postBufferData(LuciusAlertStorage.java:67) [lem_lucius.jar:6.1.0.448.474828]
at com.trigeo.core.EventToDB.postBufferToDatabase(EventToDB.java:1249) [lem_manager.jar:6.1.0.448.474828]
at com.trigeo.core.EventToDB.postBufferAlerts(EventToDB.java:1069) [lem_manager.jar:6.1.0.448.474828]
at com.trigeo.core.EventToDB.access$1300(EventToDB.java:56) [lem_manager.jar:6.1.0.448.474828]
at com.trigeo.core.EventToDB$AlertBufferReader.readSingleBuffer(EventToDB.java:347) [lem_manager.jar:6.1.0.448.474828]
at com.trigeo.core.EventToDB$AlertBufferReader.call(EventToDB.java:243) [lem_manager.jar:6.1.0.448.474828]
at com.trigeo.core.EventToDB$AlertBufferReader.call(EventToDB.java:217) [lem_manager.jar:6.1.0.448.474828]
at java.util.concurrent.FutureTask.run(Unknown Source) [na:1.7.0_67]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [na:1.7.0_67]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.7.0_67]
at java.lang.Thread.run(Unknown Source) [na:1.7.0_67]
(Wed Sep 09 19:57:36 PDT 2015) EE:ERR [LuciusDataWriter]

{BBS:DequeueToDB-1:18}

EXCEPTION: {}

 

Resolution

  1. Ensure that the Windows Agent is not Newer than version 6.1
  2. Uninstall the 6.2 Agent(s) and install the correct agent i.e. version 6.1

 

 

 

 

Last modified

Tags

Classifications

Public