systemctl Restart Hangs Because Dependency Is Deadlocked

📖 ~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

A restart command hangs while systemd waits on circular or failed dependencies.

Environment & Reproduction

systemctl shows activating state for long periods with timeout messages.

Root Cause Analysis

Unit ordering and requirement directives are inconsistent or point to unavailable services.

Quick Triage

Review dependency graph and identify failed prerequisite units.

Step-by-Step Diagnosis

Use systemctl list-dependencies , systemctl –failed, journalctl -u , and service status for legacy wrappers.

Solution – Primary Fix

Correct Wants/After directives, set practical timeouts, start prerequisite service first, and reload daemon before restart.

Solution – Alternative Approaches

Restart completes quickly and dependency chain stays healthy.

Verification & Acceptance Criteria

Revert unit override drop-ins if dependency edits cause broader impact.

Rollback Plan

Lint systemd unit dependencies during CI for infrastructure code.

Prevention & Hardening

Generate periodic reports of failed and waiting units from systemctl output.

Related Errors & Cross-Refs

Legacy SysV compatibility units can complicate dependency troubleshooting.

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

Escalate when vendor unit files need upstream correction.