Linode Out of Memory: OOM Killer Kills MySQL, Apache or Node
Quick answer
When a Linode runs out of RAM and swap, the kernel OOM killer terminates processes such as MySQL. Confirm in the kernel log, reduce memory use, add swap as a buffer, or resize to a bigger plan.
Most likely fix: Confirm the kill
How to fix it
Try these in order — the most common fix is first.
1. Confirm the kill
- Open Lish if SSH hangs
- Run sudo journalctl -k -g 'oom|out of memory|killed process'
- After a reboot use sudo journalctl -k -b -1 -g 'oom|out of memory|killed process'
- Run vmstat 1 10 and watch the si and so columns for swap thrashing
Did this fix it?2. Reduce memory use
- Lower database buffer sizes and web worker counts
- Cap Java with -Xmx below available RAM
- Find the biggest process with top or ps aux --sort=-%mem
Did this fix it?3. Add headroom
- Add a swap file as a safety buffer (not a substitute for RAM)
- Resize the Linode in Cloud Manager to a larger plan; note resizing creates a new billable service line on your invoice
Did this fix it?
Symptoms
Services such as mysqld or apache die at random, the server freezes or becomes sluggish, and the kernel log shows 'Out of memory: Kill process'.
Why it happens
- The workload needs more RAM than the plan has (1 GB Nanode is easy to exhaust)
- Swap is full or very small
- A memory-hungry process (database, Java, PHP workers) without limits
- Swap thrashing slows the machine without the killer triggering
This guide also covers
- linode out of memory
- linode oom killer
- linode mysql keeps crashing
- linode server freezes
Still not working?
If Linode keeps failing, you're not alone. See every Linode problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
All slow, laggy or resource-hungry guides →
DigitalOcean Droplet Out of Memory (OOM Killer) (DigitalOcean)
Other Linode errors
- Can't SSH Into Linode: Connection Refused or Timed Out
- Linode SSH Permission Denied (publickey)
- Linode Unreachable After Reboot, Maintenance or Firewall Change
- Linode Lish Console Not Working or Login Fails
- Linode Outbound Email Blocked: Ports 25, 465 and 587
- Linode Account Pending, Verification Required or Limit Reached
- Linode Still Charging After Powering Off: You Must Delete It
- How to Cancel Linode (Akamai Cloud) Account and Stop Billing