Find out why a process keeps dying on your server
Flavio Copes saw the claude command die within seconds on a small DigitalOcean server. He gave Codex CLI on his Mac an SSH command and a description of the problem, with no hints. The agent stated a hypothesis, read the kernel log and found the Linux out of memory killer ending the process. The server had about 2 GB of RAM and no swap. Codex listed fixes by risk and changed nothing, but he chose a costlier fix himself.
Done with CodexModerate
What was done
Flavio Copes saw the claude command die within seconds on a small DigitalOcean server. He gave Codex CLI on his Mac an SSH command and a description of the problem, with no hints. The agent stated a hypothesis, read the kernel log and found the Linux out of memory killer ending the process. The server had about 2 GB of RAM and no swap. Codex listed fixes by risk and changed nothing, but he chose a costlier fix himself.
How to do it
- Paste the prompt into the tool, and replace the text in brackets with your own.
- Read the answer through. Do not send, delete or publish anything until you have seen it yourself.
- Check the original before you trust a figure, a name or a date.
Try it with Codex
Connect to [server] with [SSH command]. The process [name] gets killed after a few seconds with no error message. Find the cause. First say what you suspect and where the evidence will be, then check logs, memory and limits. Do not change anything on the server. Show me the findings with log excerpts before you suggest fixes. You are done when the cause is proven and you have listed possible fixes sorted by risk.
Replace text in brackets with your own.
flaviocopes.com ·