Skip to content

A service disappears for no reason, OOM-kill suspected

The Linux kernel picks a process to kill when memory runs out. The choice often hits the biggest, not the guilty.

Try this first

  1. 1Check dmesg | grep -i oom or journalctl -k | grep -i oom
  2. 2Verify which process was killed and how much RSS it had
  3. 3Set oom_score_adj for critical services to protect them
  4. 4Implement cgroup memory limits per service to scope blast radius

When to bring us in

If it recurs: tune vm.overcommit_memory or add RAM, monitor with Prometheus.

See also

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.

Who are you?

For the AI question we need your email and company, so we can follow up if the AI gets stuck, and to prevent abuse.

Limited to 2 questions per hour and 5 per day, kept lean so the AI stays useful. For more, contacting us directly works better for you and us.

Or skip the DIY entirely

Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.