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

Dragonfly 1.14 Service Stopped — Exit Code 1 on SUSE Enterprise 15 SP5

PASS

The Dragonfly 1.14 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Dragonfly 1.14 Service Stopped — Exit Code 1 on Amazon Linux 2023

PASS

The Dragonfly 1.14 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Dragonfly 1.14 Service Stopped — Exit Code 1 on RHEL 9

PASS

The Dragonfly 1.14 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Dragonfly 1.14 Service Stopped — Exit Code 1 on Debian 12 Bookworm

PASS

The Dragonfly 1.14 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Dragonfly 1.14 Service Stopped — Exit Code 1 on Rocky Linux 9

PASS

The Dragonfly 1.14 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Dragonfly 1.14 Service Stopped — Exit Code 1 on CentOS 9 Stream

PASS

The Dragonfly 1.14 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Dragonfly 1.14 Service Stopped — Exit Code 1 on Ubuntu 24.04 LTS

PASS

The Dragonfly 1.14 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Dragonfly 1.14 Service Stopped — Exit Code 1 on Ubuntu 22.04 LTS

PASS

The Dragonfly 1.14 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Service Stopped — Exit Code 1 on Arch Linux

PASS

The Varnish 7.5 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Service Stopped — Exit Code 1 on Fedora 40 Server

PASS

The Varnish 7.5 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Service Stopped — Exit Code 1 on Oracle Linux 9

PASS

The Varnish 7.5 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Service Stopped — Exit Code 1 on AlmaLinux 9

PASS

The Varnish 7.5 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Service Stopped — Exit Code 1 on SUSE Enterprise 15 SP5

PASS

The Varnish 7.5 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Service Stopped — Exit Code 1 on Amazon Linux 2023

PASS

The Varnish 7.5 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Service Stopped — Exit Code 1 on RHEL 9

PASS

The Varnish 7.5 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Service Stopped — Exit Code 1 on Debian 12 Bookworm

PASS

The Varnish 7.5 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Service Stopped — Exit Code 1 on Rocky Linux 9

PASS

The Varnish 7.5 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Service Stopped — Exit Code 1 on CentOS 9 Stream

PASS

The Varnish 7.5 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Service Stopped — Exit Code 1 on Ubuntu 24.04 LTS

PASS

The Varnish 7.5 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Varnish 7.5 Service Stopped — Exit Code 1 on Ubuntu 22.04 LTS

PASS

The Varnish 7.5 service exited with code 1 due to a configuration error introduced in the last update. Service will not start until config is fixed.

cachePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal
PreviousPage 82 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.