Apache returns 503 because php-fpm is down

📖 ~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 return HTTP 503 and dynamic pages are unavailable to users.

Environment & Reproduction

RHEL 7 with httpd proxying PHP requests to php-fpm via socket or TCP.

Root Cause Analysis

php-fpm crashed, hit process limits, or socket permissions prevent Apache access.

Quick Triage

Check systemctl status php-fpm and httpd, and confirm backend socket presence.

Step-by-Step Diagnosis

Review /var/log/php-fpm/* and journalctl -u php-fpm; verify SELinux context on socket path.

Solution – Primary Fix

Correct pool settings and permissions, restart php-fpm then reload httpd.

Solution – Alternative Approaches

Temporarily switch to mod_php or a standby app node while php-fpm tuning is finalized.

Verification & Acceptance Criteria

503 errors stop, health endpoint returns 200, and php-fpm processes remain stable under load.

Rollback Plan

Restore previous php-fpm pool config and restart services if new limits regress performance.

Prevention & Hardening

Track php-fpm worker saturation and enforce baseline limits per environment profile.

Related Errors & Cross-Refs

AH01079 failed to connect to backend, php-fpm reached pm.max_children.

Related tutorial: View the step-by-step tutorial for rhel-7.

View all rhel-7 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

RHEL 7 Apache guide, php-fpm tuning docs, SELinux web server policy references.