Back to All Scenarios
PASSEDqueue / fd_exhaustion
Pulsar 3.2 File Descriptor Limit Reached on AlmaLinux 9
Pulsar 3.2 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
AlmaLinux 9. Pulsar 3.2 at 17870/17872 file descriptors. Connection leak detected. ulimit -n set to 17872 (default, not tuned for production).
Injected Error Messages (1)
Pulsar 3.2 on AlmaLinux 9 — 17870/17872 FDs used, 'Too many open files', connection refused on new requests, pulsar leaking file descriptors at 33/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: cmnhnq0r604selig7au086xqv