Log source(s) is continuously unloading and status shows that it is out of memory, but the Database is loaded.

book

Article ID: 166699

calendar_today

Updated On:

Products

Reporter

Issue/Introduction

Why is log source(s) continuously unloading and yet the status is "out of memory", but the Database is loaded?

Alert levels in Reporter for memory have reached its critical limit causing log source(s) to unload.
 
Example: Critical memory limit set to 85% (see journal file)
 
ALERT raised: Physical server memory usage has climbed above the 85% (30 GB) critical limit -- currently 88% (25.28 of 30.00 GB)
BCRJ:2014-12-17 12:46:14 (000000) ALW.ERRO.ALERT
   src/sg_alert_event_processor.cpp,0000,AlertEventProcessor::ProcessAlertEvent
      worker_thread_0000123(0000),,
   *** Please remedy this alert condition by unloading one or more databases ***
BCRJ:2014-12-17 12:46:14 (000000) ALW.ERRO.ALERT
   src/sg_alert_event_processor.cpp,000,AlertEventProcessor::ProcessAlertEvent
      worker_thread_0000123(0000),,
   *** Unloading ALL LOG SOURCES SYSTEM-WIDE because of depleted physical memory***

Resolution

To Change memory Alert Levels in Reporter to either 90 or 95%, go to the following:

  1. From Administration, navigate to General Settings > System Settings > Alerts.
  2. Increase the Alert levels to above the current level (90-95%).