Debian 9 – systemd service remains in activating state after reboot

📖 ~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 services never become active, causing prolonged application outages after restart.

Environment & Reproduction

Usually follows unit edits, dependency changes, or package updates.

# Capture baseline
systemctl --failed
systemctl status  --no-pager
systemctl cat 
journalctl -u  -n 120 --no-pager

Root Cause Analysis

Service type, readiness signaling, or dependency order does not match runtime startup behavior.

Quick Triage

Validate startup timeouts, dependency chain, and ExecStart path health.

# Quick triage
systemctl show  -p Type -p TimeoutStartUSec -p After -p Requires
which  || true

Step-by-Step Diagnosis

Trace startup path with logs and dependency graph to isolate the blocking stage.

# Detailed diagnosis
systemd-analyze critical-chain 
journalctl -b -u  --no-pager | tail -n 200
systemctl list-dependencies 

Solution – Primary Fix

Correct unit type/dependencies, reload daemon, and restart service with safe timeout values.

# Primary fix
sudo systemctl edit 
sudo systemctl daemon-reload
sudo systemctl restart 

Solution – Alternative Approaches

Use ExecStartPre checks and restart policies for transient startup races.

# Alternatives
systemctl cat 
sudo systemctl set-property  Restart=on-failure || true

Verification & Acceptance Criteria

Service transitions to active and stays healthy across restart cycles.

# Verify
systemctl status  --no-pager
systemctl is-active 
journalctl -u  -n 80 --no-pager

Rollback Plan

Revert unit override if adjustments introduce dependency regressions.

# Rollback
sudo systemctl revert 
sudo systemctl daemon-reload
sudo systemctl restart 

Prevention & Hardening

Validate unit changes in staging and apply rollout controls for service updates.

# Hardening
systemd-analyze verify /etc/systemd/system/.service
systemctl --failed

Related Errors & Cross-Refs

Associated with TimeoutStartSec exceeded and dependency failed errors.

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

systemd unit authoring and service readiness model documentation.