Find why a process dies
Codex CLI, run on the author's Mac, connected to their Ubuntu server over SSH and checked kernel logs to find why Claude Code kept dying.
Codex traced the kills to the Linux OOM killer on a 2 GB droplet with no swap, and listed fixes without changing anything.
Overview
How it was set up
Codex CLI on a Mac with SSH access to a DigitalOcean Ubuntu 24.04 droplet using a key. It read journalctl kernel logs, free, ps and ulimit output.
Worth knowing
The author resized the droplet instead of adding swap, which was the cheaper fix, and that caused later problems.
A prompt to start from
Connect to my server with [ssh command]. When I start [process] on it, it is killed within seconds. Find out why, show the evidence, and do not change anything yet.
Written by Agentic Feats from the source. Not the author's exact prompt.
Sources 1
History
- Source published
- 2026-09-15
- Added to Agentic Feats
- 2026-10-13
- Pick
- No
- Markdown copy
- /c/find-why-a-process-dies-codex.md
More in ops and IT
20 featsResultProvisioning worked after two fixes. The MCP hid the real errors, so apply ran through Cursor's Run tool, which suggested the fix.
ResultThe author migrated 10+ Lambda functions from Node.js 14 to 20 in one pass and fixed a broken docker-compose file by auto-retrying until clean.
ResultThe author runs 14 containers including Vaultwarden, Immich, Plex, and Readeck, with daily USB and weekly S3 Glacier backups costing about twenty cents per month.