Back to All Scenarios
PASSEDcache / hung_process
Redis 7.2 Process Hung — Not Responding to Health Checks on Debian 12 Bookworm
Redis 7.2 process is alive but completely unresponsive. Health checks timing out. Thread/connection pool exhausted. Requires restart.
Pattern
TIMEOUT
Severity
HIGH
Confidence
60%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | TIMEOUT | TIMEOUT | |
| Severity Assessment | HIGH | HIGH | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
Debian 12 Bookworm. Redis 7.2 PID 58947 running but not responding. All worker threads blocked. Health endpoint timing out. Last successful response 54 minutes ago.
Injected Error Messages (1)
Redis 7.2 hung on Debian 12 Bookworm — process alive (PID 58947) but timeout on all requests, ETIMEDOUT after 30s, all worker threads blocked, last response 54 minutes ago
Neural Engine Root Cause Analysis
Request timed out — service may be under heavy load, experiencing network issues, or behind a slow upstream.
Remediation Plan
Check server resource utilization (CPU/memory/disk). Investigate network path. Consider scaling if load-related.
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnq2bz04zilig78vncfaik