9 docs tagged with "startup-failure"

Detects failure when a Temporal worker is unable to reach the Temporal server.

Detects when Redpanda hits any of these on startup or early runtime\: 1. Fails to create its crash_reports directory (POSIX error 13). 2. Heartbeat or node\-status RPC failures indicating a broker is down. 3. Raft group failure. 4. Data center failure

Detects SpiceDB schema validation failures that prevent authorization

Detects critical failures where a SpiceDB instance cannot start due to an invalid schema or an uninitialized datastore during the bootstrap process. This is a common configuration error that prevents the service from initializing and serving requests, leading to a total service outage.

Exit code 127 indicates the configured command/entrypoint was not found in the image or PATH.

Detects MongoDB failures where the server enters a crash loop due to corrupted WiredTiger metadata.

Detects when Supabase self\-hosted Postgres container fails to start because another service is already using port 5432.

Detects when Supabase Auth service (GoTrue) fails to start because the configured port is already in use

Detects Envoy proxy crashes caused by assertion failures during startup or runtime.