Infrastructure Scenario Tests
We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.
Varnish 7.5 Failed to Bind Port 6081 — Already in Use on CentOS 9 Stream
PASSVarnish 7.5 cannot start because another process is already using port 6081. Service is in failed state.
Varnish 7.5 Failed to Bind Port 6081 — Already in Use on Ubuntu 24.04 LTS
PASSVarnish 7.5 cannot start because another process is already using port 6081. Service is in failed state.
Varnish 7.5 Failed to Bind Port 6081 — Already in Use on Amazon Linux 2023
PASSVarnish 7.5 cannot start because another process is already using port 6081. Service is in failed state.
Varnish 7.5 Failed to Bind Port 6081 — Already in Use on RHEL 9
PASSVarnish 7.5 cannot start because another process is already using port 6081. Service is in failed state.
KeyDB 6.3 Failed to Bind Port 6379 — Already in Use on AlmaLinux 9
PASSKeyDB 6.3 cannot start because another process is already using port 6379. Service is in failed state.
KeyDB 6.3 Failed to Bind Port 6379 — Already in Use on Oracle Linux 9
PASSKeyDB 6.3 cannot start because another process is already using port 6379. Service is in failed state.
KeyDB 6.3 Failed to Bind Port 6379 — Already in Use on Fedora 40 Server
PASSKeyDB 6.3 cannot start because another process is already using port 6379. Service is in failed state.
KeyDB 6.3 Failed to Bind Port 6379 — Already in Use on Arch Linux
PASSKeyDB 6.3 cannot start because another process is already using port 6379. Service is in failed state.
Redis 7.2 Failed to Bind Port 6379 — Already in Use on Ubuntu 22.04 LTS
PASSRedis 7.2 cannot start because another process is already using port 6379. Service is in failed state.
KeyDB 6.3 Failed to Bind Port 6379 — Already in Use on SUSE Enterprise 15 SP5
PASSKeyDB 6.3 cannot start because another process is already using port 6379. Service is in failed state.
KeyDB 6.3 Failed to Bind Port 6379 — Already in Use on Amazon Linux 2023
PASSKeyDB 6.3 cannot start because another process is already using port 6379. Service is in failed state.
KeyDB 6.3 Failed to Bind Port 6379 — Already in Use on RHEL 9
PASSKeyDB 6.3 cannot start because another process is already using port 6379. Service is in failed state.
KeyDB 6.3 Failed to Bind Port 6379 — Already in Use on Debian 12 Bookworm
PASSKeyDB 6.3 cannot start because another process is already using port 6379. Service is in failed state.
KeyDB 6.3 Failed to Bind Port 6379 — Already in Use on Rocky Linux 9
PASSKeyDB 6.3 cannot start because another process is already using port 6379. Service is in failed state.
KeyDB 6.3 Failed to Bind Port 6379 — Already in Use on CentOS 9 Stream
PASSKeyDB 6.3 cannot start because another process is already using port 6379. Service is in failed state.
KeyDB 6.3 Failed to Bind Port 6379 — Already in Use on Ubuntu 24.04 LTS
PASSKeyDB 6.3 cannot start because another process is already using port 6379. Service is in failed state.
KeyDB 6.3 Failed to Bind Port 6379 — Already in Use on Ubuntu 22.04 LTS
PASSKeyDB 6.3 cannot start because another process is already using port 6379. Service is in failed state.
Memcached 1.6 Failed to Bind Port 11211 — Already in Use on Arch Linux
PASSMemcached 1.6 cannot start because another process is already using port 11211. Service is in failed state.
Memcached 1.6 Failed to Bind Port 11211 — Already in Use on Fedora 40 Server
PASSMemcached 1.6 cannot start because another process is already using port 11211. Service is in failed state.
Memcached 1.6 Failed to Bind Port 11211 — Already in Use on Oracle Linux 9
PASSMemcached 1.6 cannot start because another process is already using port 11211. 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.