Back to All Scenarios
PASSEDqueue / service_crash
ZeroMQ 4.3 Out of Memory — Killed by OOM Killer on AlmaLinux 9
The Linux OOM killer terminated the ZeroMQ 4.3 process due to memory pressure. The service was the largest memory consumer on the system.
Pattern
MEMORY_EXHAUSTION
Severity
CRITICAL
Confidence
72%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | MEMORY_EXHAUSTION | MEMORY_EXHAUSTION | |
| Severity Assessment | CRITICAL | CRITICAL | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
AlmaLinux 9. ZeroMQ 4.3 consuming 7GB RAM. OOM killer score: 878. System had 30GB total. No swap configured.
Injected Error Messages (1)
Out of memory: oom-killer terminated process 26242 (zeromq) total-vm:7340032kB on AlmaLinux 9, ZeroMQ 4.3 port 5555 down, memory critical, no swap available, 200 users/connections connections dropped
Neural Engine Root Cause Analysis
Memory exhaustion detected — the system has run out of available memory, triggering the OOM killer or forcing heavy swap usage. This causes severe performance degradation and can result in random process termination. Memory leaks in long-running applications are a common root cause, especially after deployments or configuration changes.
Remediation Plan
1. Check which process was OOM-killed using 'dmesg | grep -i oom' or journal logs.
2. Review memory usage by process with 'ps aux --sort=-%mem | head -20'.
3. Restart the affected service to reclaim leaked memory.
4. If a memory leak is suspected, enable heap profiling and analyze memory allocation patterns.
5. Consider increasing server memory or setting appropriate memory limits (cgroups/container limits).
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnp5ml01nqlig7zd5ofmdu