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

Apache Kafka 3.7 Failed to Bind Port 9092 — Already in Use on SUSE Enterprise 15 SP5

PASS

Apache Kafka 3.7 cannot start because another process is already using port 9092. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Apache Kafka 3.7 Failed to Bind Port 9092 — Already in Use on Amazon Linux 2023

PASS

Apache Kafka 3.7 cannot start because another process is already using port 9092. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Apache Kafka 3.7 Failed to Bind Port 9092 — Already in Use on RHEL 9

PASS

Apache Kafka 3.7 cannot start because another process is already using port 9092. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Apache Kafka 3.7 Failed to Bind Port 9092 — Already in Use on Debian 12 Bookworm

PASS

Apache Kafka 3.7 cannot start because another process is already using port 9092. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Apache Kafka 3.7 Failed to Bind Port 9092 — Already in Use on Rocky Linux 9

PASS

Apache Kafka 3.7 cannot start because another process is already using port 9092. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Apache Kafka 3.7 Failed to Bind Port 9092 — Already in Use on CentOS 9 Stream

PASS

Apache Kafka 3.7 cannot start because another process is already using port 9092. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Apache Kafka 3.7 Failed to Bind Port 9092 — Already in Use on Ubuntu 24.04 LTS

PASS

Apache Kafka 3.7 cannot start because another process is already using port 9092. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Apache Kafka 3.7 Failed to Bind Port 9092 — Already in Use on Ubuntu 22.04 LTS

PASS

Apache Kafka 3.7 cannot start because another process is already using port 9092. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed to Bind Port 5672 — Already in Use on Arch Linux

PASS

RabbitMQ 3.13 cannot start because another process is already using port 5672. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed to Bind Port 5672 — Already in Use on Fedora 40 Server

PASS

RabbitMQ 3.13 cannot start because another process is already using port 5672. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed to Bind Port 5672 — Already in Use on Oracle Linux 9

PASS

RabbitMQ 3.13 cannot start because another process is already using port 5672. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed to Bind Port 5672 — Already in Use on AlmaLinux 9

PASS

RabbitMQ 3.13 cannot start because another process is already using port 5672. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed to Bind Port 5672 — Already in Use on SUSE Enterprise 15 SP5

PASS

RabbitMQ 3.13 cannot start because another process is already using port 5672. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed to Bind Port 5672 — Already in Use on Amazon Linux 2023

PASS

RabbitMQ 3.13 cannot start because another process is already using port 5672. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed to Bind Port 5672 — Already in Use on RHEL 9

PASS

RabbitMQ 3.13 cannot start because another process is already using port 5672. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed to Bind Port 5672 — Already in Use on Debian 12 Bookworm

PASS

RabbitMQ 3.13 cannot start because another process is already using port 5672. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed to Bind Port 5672 — Already in Use on Rocky Linux 9

PASS

RabbitMQ 3.13 cannot start because another process is already using port 5672. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed to Bind Port 5672 — Already in Use on CentOS 9 Stream

PASS

RabbitMQ 3.13 cannot start because another process is already using port 5672. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed to Bind Port 5672 — Already in Use on Ubuntu 24.04 LTS

PASS

RabbitMQ 3.13 cannot start because another process is already using port 5672. Service is in failed state.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed to Bind Port 5672 — Already in Use on Ubuntu 22.04 LTS

PASS

RabbitMQ 3.13 cannot start because another process is already using port 5672. Service is in failed state.

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