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