Tag: Startup Failure

Problems related to application or service startup failures, such as missing dependencies or configuration errors

ID	Title	Description	Category	Technology	Tags
CRE-2025-0074 Critical Impact: 10/10 Mitigation: 6/10	Temporal Worker → Server Downtime → Connection Refused Failure	Detects failure when a Temporal worker is unable to reach the Temporal server. - This typically occurs during startup or after server downtime. - Worker log contains gRPC error: "connection refused".	Workflow Orchestration Connectivity	worker	Temporal Worker Problems gRPC Connection Refused Startup Failure
CRE-2025-0080 High Impact: 0/10 Mitigation: 9/10	Redpanda High Severity Issues	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	Data Streaming Platforms	redpanda	Redpanda Startup Failure Permission Failure RPC Raft Node Down Cluster Degradation Data Availability Database Corruption
CRE-2025-0085 High Impact: 8/10 Mitigation: 7/10	SpiceDB Schema Validation Failures Block Authorization Updates	Detects SpiceDB schema validation failures that prevent authorization logic updates and deployments. These failures occur when invalid schema definitions are submitted, including syntax errors, circular dependencies, type conflicts, or malformed permission expressions, blocking critical authorization system updates.	Authorization Problems	spicedb	SpiceDB Authorization Configuration Validation Crash Startup Failure
CRE-2025-0105 High Impact: 9/10 Mitigation: 3/10	SpiceDB Datastore Startup Failure	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.	Authorization Systems	spicedb	SpiceDB Authorization Datastore Misconfiguration Startup Failure
CRE-2025-0127 Medium Impact: 3/10 Mitigation: 3/10	Container exited 127 due to command not found (bad entrypoint/command)	Exit code 127 indicates the configured command/entrypoint was not found in the image or PATH. New or misconfigured deployments commonly hit this and immediately crash.	Configuration Problem	kubernetes	K8s Exit Code Command Entrypoint Startup Failure
CRE-2025-0129 Critical Impact: 10/10 Mitigation: 9/10	MongoDB Crash Loop Due to WiredTiger Metadata Corruption	Detects MongoDB failures where the server enters a crash loop due to corrupted WiredTiger metadata. This prevents startup and often requires manual repair or restoration from backups.	MongoDB Startup Failure	mongodb	MongoDB WiredTiger Metadata Corruption Crash Loop Startup Failure
CRE-2025-0130 High Impact: 9/10 Mitigation: 3/10	Supabase Self-Hosted: Postgres Container Fails to Start Due to Port Conflict	Detects when Supabase self-hosted Postgres container fails to start because another service is already using port 5432. This is a common issue during initial setup or when multiple Postgres instances are running on the same host. The failure prevents the entire Supabase stack from starting properly.	Database Problems	supabase	Supabase PostgreSQL Port Binding Configuration Startup Failure Self-Hosted Container Crash Public
CRE-2025-0136 Medium Impact: 8/10 Mitigation: 3/10	Supabase Self-Hosted: Auth Service Fails Due to Port Binding Conflict	Detects when Supabase Auth service (GoTrue) fails to start because the configured port is already in use by another service. This prevents user authentication, registration, and all auth-related operations from functioning in the self-hosted Supabase deployment.	authentication	docker	Supabase Authentication Port Binding Configuration Startup Failure Self-Hosted GoTrue Public