Infrastructure Scenario Tests

We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.

21,502
Total Tests
100.0%
Pass Rate
21,502
Passed
0
Failed

ZeroMQ 4.3 Startup Timeout — Taking Too Long to Initialize on Amazon Linux 2023

PASS

ZeroMQ 4.3 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

MSMQ Startup Timeout — Taking Too Long to Initialize on Windows 10 Enterprise

PASS

MSMQ is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

MSMQ Startup Timeout — Taking Too Long to Initialize on Windows 11 Enterprise

PASS

MSMQ is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

MSMQ Startup Timeout — Taking Too Long to Initialize on Windows Server 2019

PASS

MSMQ is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

MSMQ Startup Timeout — Taking Too Long to Initialize on Windows Server 2022

PASS

MSMQ is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ZeroMQ 4.3 Startup Timeout — Taking Too Long to Initialize on Arch Linux

PASS

ZeroMQ 4.3 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ZeroMQ 4.3 Startup Timeout — Taking Too Long to Initialize on Fedora 40 Server

PASS

ZeroMQ 4.3 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ZeroMQ 4.3 Startup Timeout — Taking Too Long to Initialize on Debian 12 Bookworm

PASS

ZeroMQ 4.3 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ZeroMQ 4.3 Startup Timeout — Taking Too Long to Initialize on Rocky Linux 9

PASS

ZeroMQ 4.3 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ZeroMQ 4.3 Startup Timeout — Taking Too Long to Initialize on RHEL 9

PASS

ZeroMQ 4.3 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ZeroMQ 4.3 Startup Timeout — Taking Too Long to Initialize on CentOS 9 Stream

PASS

ZeroMQ 4.3 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ZeroMQ 4.3 Startup Timeout — Taking Too Long to Initialize on Oracle Linux 9

PASS

ZeroMQ 4.3 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ZeroMQ 4.3 Startup Timeout — Taking Too Long to Initialize on AlmaLinux 9

PASS

ZeroMQ 4.3 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ZeroMQ 4.3 Startup Timeout — Taking Too Long to Initialize on SUSE Enterprise 15 SP5

PASS

ZeroMQ 4.3 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ActiveMQ 6.1 Startup Timeout — Taking Too Long to Initialize on Arch Linux

PASS

ActiveMQ 6.1 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ActiveMQ 6.1 Startup Timeout — Taking Too Long to Initialize on Fedora 40 Server

PASS

ActiveMQ 6.1 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ActiveMQ 6.1 Startup Timeout — Taking Too Long to Initialize on Oracle Linux 9

PASS

ActiveMQ 6.1 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ActiveMQ 6.1 Startup Timeout — Taking Too Long to Initialize on AlmaLinux 9

PASS

ActiveMQ 6.1 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ActiveMQ 6.1 Startup Timeout — Taking Too Long to Initialize on SUSE Enterprise 15 SP5

PASS

ActiveMQ 6.1 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ActiveMQ 6.1 Startup Timeout — Taking Too Long to Initialize on Amazon Linux 2023

PASS

ActiveMQ 6.1 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal
PreviousPage 61 of 116Next

Every scenario is tested against Corax's Neural Engine in a production environment with AI-powered root cause analysis.

Tests run continuously as new infrastructure patterns are added.