Debian 9 – OOM killer terminates critical services under load – Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Critical processes are killed unexpectedly, causing application outages and transaction loss.

Environment & Reproduction

Appears during traffic spikes, batch workloads, or memory leaks in long-running services.

Root Cause Analysis

Total committed memory exceeds limits and kernel OOM policy selects victim processes.

Quick Triage

Capture OOM log lines and identify repeat victim patterns before restarting everything.

Step-by-Step Diagnosis

Analyze memory footprints over time and map killers to service roles and priorities.

Solution – Primary Fix

Increase headroom, tune service memory limits, and apply process priority safeguards.

Solution – Alternative Approaches

Split workloads across nodes to reduce single-host memory contention and blast radius.

Verification & Acceptance Criteria

No OOM events occur during peak test scenarios and critical services remain available.

Rollback Plan

Revert limit and kernel changes if tuning destabilizes scheduler or workload behavior.

Prevention & Hardening

Implement memory SLOs, leak detection, and cgroup-based protection for key daemons.

Related Errors & Cross-Refs

Closely linked with swap thrashing and runaway process memory growth patterns.

Related tutorial: View the step-by-step tutorial for Debian 9.

View all Debian 9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Linux OOM handling and capacity planning guidance for reliable service operation.