Debian 9 – critical systemd service fails to start after reboot – 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

Required service remains failed after boot, causing outage or degraded functionality.

Environment & Reproduction

Appears after package updates or manual unit edits.

systemctl --failed
systemctl status myapp.service
sudo reboot

Root Cause Analysis

Invalid unit settings, ordering conflicts, or missing dependencies block startup.

Quick Triage

Capture unit logs and dependency metadata quickly.

journalctl -b -u myapp.service --no-pager
systemctl show -p After -p Requires myapp.service
systemctl cat myapp.service

Step-by-Step Diagnosis

Validate unit syntax and inspect critical chain ordering.

sudo systemd-analyze verify /etc/systemd/system/myapp.service
systemd-analyze critical-chain myapp.service
sudo ls -l /etc/systemd/system/myapp.service.d

Solution – Primary Fix

Correct unit directives, reload daemon, and start cleanly.

sudo systemctl edit --full myapp.service
sudo systemctl daemon-reload
sudo systemctl enable --now myapp.service
sudo systemctl reset-failed myapp.service

Solution – Alternative Approaches

Use drop-in override to avoid touching packaged unit files.

sudo mkdir -p /etc/systemd/system/myapp.service.d
sudo tee /etc/systemd/system/myapp.service.d/override.conf >/dev/null <<'EOF'
[Service]
Restart=on-failure
RestartSec=5
EOF
sudo systemctl daemon-reload

Verification & Acceptance Criteria

Service remains active across reboot with no recurring errors.

systemctl is-enabled myapp.service
systemctl is-active myapp.service
journalctl -b -u myapp.service -n 40 --no-pager

Rollback Plan

Remove override and restore previous unit behavior if needed.

sudo rm -f /etc/systemd/system/myapp.service.d/override.conf
sudo systemctl daemon-reload
sudo systemctl restart myapp.service

Prevention & Hardening

Validate unit changes in staging and monitor failed-unit alerts.

systemctl --failed
systemd-analyze verify /etc/systemd/system/*.service

Related Errors & Cross-Refs

Often linked with mount-order issues and missing runtime directories.

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

Debian systemd service management documentation.