About Get Started

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

All Categories Server (9315)Database (5486)Infrastructure (2435)queue (2320)cache (1740)Network (81)Cloud (78)Security (36)VoIP (7)Cascade (4)

All Status Passed Failed

Varnish 7.5 Startup Timeout — Taking Too Long to Initialize on Rocky Linux 9

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Startup Timeout — Taking Too Long to Initialize on CentOS 9 Stream

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Startup Timeout — Taking Too Long to Initialize on Ubuntu 24.04 LTS

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Startup Timeout — Taking Too Long to Initialize on Ubuntu 22.04 LTS

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

KeyDB 6.3 Startup Timeout — Taking Too Long to Initialize on Rocky Linux 9

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

KeyDB 6.3 Startup Timeout — Taking Too Long to Initialize on Arch Linux

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

KeyDB 6.3 Startup Timeout — Taking Too Long to Initialize on Fedora 40 Server

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

KeyDB 6.3 Startup Timeout — Taking Too Long to Initialize on Oracle Linux 9

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

KeyDB 6.3 Startup Timeout — Taking Too Long to Initialize on AlmaLinux 9

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

KeyDB 6.3 Startup Timeout — Taking Too Long to Initialize on SUSE Enterprise 15 SP5

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

KeyDB 6.3 Startup Timeout — Taking Too Long to Initialize on Amazon Linux 2023

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

KeyDB 6.3 Startup Timeout — Taking Too Long to Initialize on RHEL 9

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

KeyDB 6.3 Startup Timeout — Taking Too Long to Initialize on Debian 12 Bookworm

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

KeyDB 6.3 Startup Timeout — Taking Too Long to Initialize on CentOS 9 Stream

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

KeyDB 6.3 Startup Timeout — Taking Too Long to Initialize on Ubuntu 24.04 LTS

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

KeyDB 6.3 Startup Timeout — Taking Too Long to Initialize on Ubuntu 22.04 LTS

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Memcached 1.6 Startup Timeout — Taking Too Long to Initialize on Arch Linux

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Memcached 1.6 Startup Timeout — Taking Too Long to Initialize on Fedora 40 Server

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Memcached 1.6 Startup Timeout — Taking Too Long to Initialize on Oracle Linux 9

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Memcached 1.6 Startup Timeout — Taking Too Long to Initialize on AlmaLinux 9

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

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

PreviousPage 50 of 87Next

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.