systemctl can't read symlinks to SysVinit service scripts in /etc/init.d after upgrading to RHEL 7.2's systemd-219-19.el7

Solution Verified - Updated -


  • The rebase of systemd in RHEL 7.2 seems to have broken something with SysVinit compatibility
    If a service script resides directly in /etc/init.d/, all is well; however, if /etc/init.d/<SERVICE> is a symlink, all systemctl and service commands fail with:

    Unit <SERVICE>.service failed to load: No such file or directory.


  • Red Hat Enterprise Linux 7
    • systemd-219-19.el7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content