RHEL 9 Service Starts Manually but Not on Boot

📖 ~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 service can be started with systemctl manually but does not come up automatically during boot.

Environment & Reproduction

After reboot, the service is inactive and dependent applications fail until manual intervention.

Root Cause Analysis

Unit not enabled, wrong target dependency, race condition with network/storage readiness, or failed pre-check.

Quick Triage

Run ‘sudo systemctl is-enabled ‘ and inspect install targets in the unit definition.

Step-by-Step Diagnosis

Use ‘sudo systemctl enable ‘ and confirm symlinks under target wants directories.

Solution – Primary Fix

Review ‘sudo journalctl -b -u –no-pager’ for ordering and dependency failures.

Solution – Alternative Approaches

Add or adjust After= and Wants= entries for network-online.target or required mounts as needed.

Verification & Acceptance Criteria

When unit files change, apply with ‘sudo systemctl daemon-reload’ before reboot testing.

Rollback Plan

Ensure startup scripts and config paths have correct permissions and SELinux labels for boot context.

Prevention & Hardening

If service depends on network exposure, verify firewalld loads expected rules by boot completion.

Related Errors & Cross-Refs

Perform a controlled reboot and verify service status plus functional endpoint checks immediately afterward.

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

View all rhel-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Add boot-time health checks to configuration management and fail deployments when auto-start is broken.