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.
support/performance/oom-killer-logssteps: 4
Try this first
- Check dmesg | grep -i oom or journalctl -k | grep -i oom
- Verify which process was killed and how much RSS it had
- Set oom_score_adj for critical services to protect them
- Implement 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
- My laptop is suddenly slowThree main suspects: a runaway background process, near-full disk, or a Windows update in progress.
- One specific application is slow for everyoneIf an app is slow for one person: local. For everyone at once: server side or vendor side.
- Opening files from the file server takes minutesOften the server itself is fine and the issue is network routing or stalling DNS resolution.
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.
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.