RHEL 7 Legacy service Script Conflicts with systemctl Unit

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

Operators get inconsistent status and restart results when mixing service and systemctl commands. This causes confusion and intermittent outages.

Environment & Reproduction

Typical on upgraded RHEL 7 hosts with legacy init scripts still present. yum package transitions can leave both control paths available.

Root Cause Analysis

A wrapper script and native unit diverge in expectations, PID files, or environment variables. journalctl records conflicting start/stop actions.

Quick Triage

Compare service output to systemctl status and systemctl cat. Check journalctl timeline, verify SELinux contexts, and ensure firewalld is not masking app health.

Step-by-Step Diagnosis

Identify authoritative startup path, inspect PID and lock handling, and test command parity. Correlate with yum package ownership for init scripts.

Solution – Primary Fix

Standardize on systemctl-managed unit, retire conflicting legacy script behaviors, and update runbooks. Restart and verify service stability with journalctl evidence.

Solution – Alternative Approaches

Wrap legacy controls into a compatibility shim temporarily, or vendor-pin package versions until full migration is complete.

Verification & Acceptance Criteria

Status, start, stop, and restart actions are consistent from the approved control path. No duplicate process or stale PID behavior remains.

Rollback Plan

Reinstate prior script behavior if emergency fallback is required, and revert package changes with yum history as needed.

Prevention & Hardening

Define one operational control interface, enforce via automation linting, and monitor command misuse through shell history and audit events.

Related Errors & Cross-Refs

Related issues include orphaned processes and stale lock files. See linked tutorial 9072 for legacy-to-systemd migration guidance.

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

Read man systemctl, man service, man systemd.service, man yum, man firewall-cmd, SELinux docs, and man journalctl.