Back to All Scenarios
PASSEDqueue / fd_exhaustion
RabbitMQ 3.13 File Descriptor Limit Reached on RHEL 9
RabbitMQ 3.13 has exhausted its file descriptor limit. Cannot accept new connections or open new files. Service functionality severely degraded.
Pattern
CONNECTION_REFUSED
Severity
CRITICAL
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | CONNECTION_REFUSED | CONNECTION_REFUSED | |
| Severity Assessment | HIGH | CRITICAL | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
RHEL 9. RabbitMQ 3.13 at 1275/1275 file descriptors. Connection leak detected. ulimit -n set to 1275 (default, not tuned for production).
Injected Error Messages (1)
RabbitMQ 3.13 on RHEL 9 — 1275/1275 FDs used, 'Too many open files', connection refused on new requests, rabbitmq-server leaking file descriptors at 10/min
Neural Engine Root Cause Analysis
Connection refused — service is likely crashed or not listening on the expected port.
Remediation Plan
Restart the target service. If recurring, check for memory leaks or crash loops.
Improvements Applied
- Severity: CRITICAL (expected HIGH)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnpyda04knlig73hc9izy9