Back to All Scenarios
PASSEDqueue / connection_storm
Pulsar 3.2 Connection Storm — SYN Flood or Client Bug on Fedora 40 Server
Pulsar 3.2 is receiving thousands of new connections per second, overwhelming the accept queue. Legitimate connections being dropped.
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
Fedora 40 Server. Pulsar 3.2 seeing 40744 new connections/sec (normal: 169). SYN backlog full. accept queue overflowing. net.core.somaxconn=3279.
Injected Error Messages (1)
Pulsar 3.2 on Fedora 40 Server — connection refused for legitimate clients, 40744 new conns/sec (normal: 169), SYN backlog full, accept queue overflow, ECONNREFUSED
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: cmnhnr1bw08nclig7dvyqr278