Debian 10 – PHP-FPM pool crashes from memory limit exhaustion – 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

Web requests fail intermittently as PHP workers terminate under load.

Environment & Reproduction

Triggered by traffic bursts or inefficient scripts with low memory headroom.

Root Cause Analysis

Pool process limits and per-worker memory exceed available resources.

Quick Triage

Check OOM signals, pool status, and request backlog immediately.

Step-by-Step Diagnosis

Correlate slow logs, memory usage, and process manager settings.

Solution – Primary Fix

Tune pm settings, memory_limit, and worker counts to safe envelope.

Solution – Alternative Approaches

Scale horizontally or cache expensive operations to reduce PHP pressure.

Verification & Acceptance Criteria

No worker crash loops and acceptable latency at expected peak.

Rollback Plan

Restore previous FPM profile if new limits underutilize resources.

Prevention & Hardening

Load-test periodically and enforce performance budgets in releases.

Related Errors & Cross-Refs

Related to 502/504 gateway errors and kernel OOM killer events.

Related tutorial: View the step-by-step tutorial for debian-10.

View all debian-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

PHP-FPM tuning and Linux memory management references.