The 30-Second Death: A Memoir

A true story about a database that died on a schedule, a developer who tried everything, and a CPU security feature nobody told anyone about. My database kept dying. Every. Thirty. Seconds. Not crashing with an error. Not leaving a note. Just... gone. Exit code 139. No explanation. No apology. I checked the logs. MongoDB had started successfully. Recovered from the previous unclean shutdown. Accepted connections. Everything looked fine. Then it died. Act I: Blame the Obvious Thing Me: Why is the DB crashing? MongoDB: dies Me: Okay, unclean shutdown, probably just needs to recover— MongoDB: recovers successfully, then dies again I did what any reasonable engineer does. I blamed the obvious thing. "It's mongo:latest ," I said confidently. "Never trust latest ." I pinned the version. mongo:8.0.14-noble . Stable. Specific. Professional. image : mongo:8.0.14-noble MongoDB: dies at exactly 30 seconds Act II: Disable Everything Fine. The diagnostics collector — FTDC. It reads /proc files in t