Tag: Crash Loop
Repeated failure to start or recover due to a persistent internal problem, such as corrupted state or misconfiguration.
| ID | Title | Description | Category | Technology | Tags |
|---|---|---|---|---|---|
| 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 | MongoDBWiredTigerMetadataCorruptionCrash LoopStartup Failure |
| CRE-2025-0137 High Impact: 6/10 Mitigation: 2/10 | Pod terminated with Exit Code 137 due to OOMKilled (memory limit exceeded) | The container exceeded its memory limit and was killed by the kernel OOM killer. Kubernetes reports a terminated state with Reason=OOMKilled and exitCode=137. This often manifests as CrashLoopBackOff under sustained memory pressure. | Memory Problems | kubernetes | K8sExit CodeOut of MemoryMemoryCrash LoopReliability |