Infrastructure Scenario Tests
We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.
Pulsar 3.2 Failed to Bind Port 6650 — Already in Use on AlmaLinux 9
PASSPulsar 3.2 cannot start because another process is already using port 6650. Service is in failed state.
Pulsar 3.2 Failed to Bind Port 6650 — Already in Use on SUSE Enterprise 15 SP5
PASSPulsar 3.2 cannot start because another process is already using port 6650. Service is in failed state.
Pulsar 3.2 Failed to Bind Port 6650 — Already in Use on RHEL 9
PASSPulsar 3.2 cannot start because another process is already using port 6650. Service is in failed state.
Pulsar 3.2 Failed to Bind Port 6650 — Already in Use on Debian 12 Bookworm
PASSPulsar 3.2 cannot start because another process is already using port 6650. Service is in failed state.
Pulsar 3.2 Failed to Bind Port 6650 — Already in Use on Rocky Linux 9
PASSPulsar 3.2 cannot start because another process is already using port 6650. Service is in failed state.
Pulsar 3.2 Failed to Bind Port 6650 — Already in Use on CentOS 9 Stream
PASSPulsar 3.2 cannot start because another process is already using port 6650. Service is in failed state.
Pulsar 3.2 Failed to Bind Port 6650 — Already in Use on Ubuntu 24.04 LTS
PASSPulsar 3.2 cannot start because another process is already using port 6650. Service is in failed state.
Pulsar 3.2 Failed to Bind Port 6650 — Already in Use on Ubuntu 22.04 LTS
PASSPulsar 3.2 cannot start because another process is already using port 6650. Service is in failed state.
ActiveMQ 6.1 Failed to Bind Port 61616 — Already in Use on Windows 10 Enterprise
PASSActiveMQ 6.1 cannot start because another process is already using port 61616. Service is in failed state.
ActiveMQ 6.1 Failed to Bind Port 61616 — Already in Use on Windows 11 Enterprise
PASSActiveMQ 6.1 cannot start because another process is already using port 61616. Service is in failed state.
ActiveMQ 6.1 Failed to Bind Port 61616 — Already in Use on Windows Server 2019
PASSActiveMQ 6.1 cannot start because another process is already using port 61616. Service is in failed state.
ActiveMQ 6.1 Failed to Bind Port 61616 — Already in Use on Windows Server 2022
PASSActiveMQ 6.1 cannot start because another process is already using port 61616. Service is in failed state.
ActiveMQ 6.1 Failed to Bind Port 61616 — Already in Use on Arch Linux
PASSActiveMQ 6.1 cannot start because another process is already using port 61616. Service is in failed state.
ActiveMQ 6.1 Failed to Bind Port 61616 — Already in Use on Fedora 40 Server
PASSActiveMQ 6.1 cannot start because another process is already using port 61616. Service is in failed state.
ActiveMQ 6.1 Failed to Bind Port 61616 — Already in Use on Oracle Linux 9
PASSActiveMQ 6.1 cannot start because another process is already using port 61616. Service is in failed state.
ActiveMQ 6.1 Failed to Bind Port 61616 — Already in Use on AlmaLinux 9
PASSActiveMQ 6.1 cannot start because another process is already using port 61616. Service is in failed state.
ActiveMQ 6.1 Failed to Bind Port 61616 — Already in Use on SUSE Enterprise 15 SP5
PASSActiveMQ 6.1 cannot start because another process is already using port 61616. Service is in failed state.
ActiveMQ 6.1 Failed to Bind Port 61616 — Already in Use on Amazon Linux 2023
PASSActiveMQ 6.1 cannot start because another process is already using port 61616. Service is in failed state.
ActiveMQ 6.1 Failed to Bind Port 61616 — Already in Use on RHEL 9
PASSActiveMQ 6.1 cannot start because another process is already using port 61616. Service is in failed state.
ActiveMQ 6.1 Failed to Bind Port 61616 — Already in Use on Debian 12 Bookworm
PASSActiveMQ 6.1 cannot start because another process is already using port 61616. Service is in failed state.
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.