Back to All Scenarios
PASSEDqueue / pending_restart
RabbitMQ 3.13 Running Outdated Binary — Restart Required After Update on SUSE Enterprise 15 SP5
RabbitMQ 3.13 package was updated but the service was not restarted. Running old binary with known vulnerability. Needs-restarting flag set.
Pattern
PERFORMANCE_DEGRADATION
Severity
MEDIUM
Confidence
51%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | PERFORMANCE_DEGRADATION | PERFORMANCE_DEGRADATION | |
| Severity Assessment | MEDIUM | MEDIUM | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
SUSE Enterprise 15 SP5. RabbitMQ 3.13 package updated via apt/yum. Process still running old binary (deleted). needs-restarting check: true. Known CVE in running version.
Injected Error Messages (1)
RabbitMQ 3.13 degraded on SUSE Enterprise 15 SP5 — running deleted binary, package updated but not restarted, response time degraded, /proc/13308/exe points to deleted file, needs-restarting: true
Neural Engine Root Cause Analysis
Performance degradation detected — response times are significantly above baseline, indicating resource pressure, increased load, or infrastructure issues.
Remediation Plan
Investigate server resource usage (CPU, memory, disk I/O). Check for background jobs or traffic spikes. Optimize slow queries or endpoints if specific to one service.
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnqrwy07shlig7ofoimt7e