Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

VPS & Linux

Linux OOM troubleshooting: find what exhausted memory

Published August 2026 · 2 min read · Updated 2026-09-05

The Linux OOM killer is a last-resort response when the kernel cannot satisfy memory allocations under the current constraints. The process it kills is evidence of a system-wide pressure event; it is not always the process that originally caused the memory problem.

Read the kernel record first

Use journalctl or kernel logs to find the OOM event, cgroup context, memory totals, process scores, and killed process. Container or service limits can trigger an OOM inside a cgroup even when the whole VPS still has memory available.

Preserve the timestamp and the process table around the event if monitoring has it. Restarting the application restores service but removes useful context.

Find growth before the kill

Compare memory time series, worker counts, queue depth, request concurrency, database/cache sizes, imports, builds, and deployments. A leak often shows a steady trend; a batch job may create a sharp temporary peak.

Check whether swap was available and whether the system was already reclaiming aggressively.

Reduce the actual allocation pressure

Fix leaks, bound concurrency, cap queues, tune oversized caches or heaps, and move large maintenance jobs when those are the cause. Service-level memory limits can protect the rest of the server, but a limit that is too low simply moves the OOM boundary inward.

Do not disable the OOM killer; a system that cannot reclaim or terminate anything may become less recoverable.

Resize when the healthy peak is legitimate

If the measured working set and legitimate peak do not fit the plan after tuning, add memory. Retest the same scenario and verify that application latency, memory pressure and restart behavior improve and that the change does more than delay another kill.

  • Capture the kernel OOM record.
  • Check cgroup versus host pressure.
  • Find the growth pattern before the event.
  • Retest after tuning or resize.

Next step

Read OOM-killer logs, process memory, cgroup limits and workload timing to identify why Linux killed a process and what should change next.

Explore DotMoose VPS hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Linux file permissions: ownership, modes, groups and ACLs explained

Understand Unix ownership and rwx modes, then use groups and ACLs where needed so services can access files without opening them to every user.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More vps & linux guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move