Back to All Scenarios
PASSEDserver / socket_leak
Ruby 3.3 (Puma) Socket Leak — Ephemeral Ports Exhausted on AlmaLinux 9
Ruby 3.3 (Puma) has a socket leak causing ephemeral port exhaustion. Cannot create new outbound connections. TIME_WAIT count critical.
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. Ruby 3.3 (Puma) with 24415 sockets in TIME_WAIT. Ephemeral port range exhausted (32768-60999). New connections failing with EADDRNOTAVAIL.
Injected Error Messages (1)
Ruby 3.3 (Puma) on AlmaLinux 9 — ephemeral ports exhausted, connection refused on new outbound connections, 24415 sockets in TIME_WAIT, ECONNREFUSED, puma socket leak detected
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: cmnhnw1cf03eklijgju6149z0