Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: Insight Host Agent|
Host Insight Agent Error: Unable to allocate memory. Cause: This indicates a low memory condition. Rebooting the system will correct this error.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What may cause a low memory condition?
This indicates a Memory Leak caused by Insight Agent.
From a newsgroup post: I have a client that was severely impacted by the SNMP memory leak in SP4 (heavy compaq Insight Manager use and a smattering of other SNMP-enabled services and applications). They upgraded to SP5 and upgraded the Insight Agents. The leak came back after a few weeks (event ID 2048 from Insight Host Agent filling system event log, just like under SP4). It now appears that the servers that were most severely affected (some had no problems at all on SP4 with Insight Agent versions 3.40-4.10) were configured to send traps to "dead" IP addresses. The servers without memory leaks are correctly configured.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated