[DOCS-6945] Ops Manager init.d scripts are not started at boot on RHEL 7.1/7.2 (systemd-219-19.el7) Created: 08/Jan/16  Updated: 24/Feb/16  Resolved: 12/Jan/16

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: ops-manager-2.0.0

Type: Task Priority: Critical - P2
Reporter: Emilio Scalise Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RHEL 7.1 or 7.2 using systemd-219-19.el7


Issue Links:
Related
Participants:
Days since reply: 8 years, 5 weeks, 5 days ago

 Description   

Ops Manager init.d scripts are not started at boot on Redhat Enterprise Linux 7.1 and 7.2 (systemd-219-19.el7) due to Bug 1285492.

This SystemD bug leads to failure executing the SysVInit style scripts being referenced by symbolic links from /etc/init.d at boot.

Ops Manager makes use of such symlinks.

A workaround is to copy the init.d scripts from /opt/mongodb/mms/bin/mongodb-mms (and /opt/mongodb/mms/bin/mongodb-mms-backup-daemon for Ops Manager 1.8.x and lower) and change the line:

ABS_PATH="$( resolvepath $0 )"

to:

SCRIPTPATH=/opt/mongodb/mms/bin/mongodb-mms
ABS_PATH="$( resolvepath $SCRIPTPATH )"

An official fix for the Redhat Bug is still being worked on. Meanwhile this should be at least documented or worked around.

Previous versions of SystemD like the one that can be found in Redhat 7.0 (systemd-208-11.el7.x86_64) are not affected by this issue.

Kind regards,
Emilio



 Comments   
Comment by Cailin Nelson [ 08/Jan/16 ]

Let's document this, and keep an eye on the RedHat bug. It has "Priority: High" and label "EasyFix", so hopefully it will get done.

Generated at Thu Feb 08 07:53:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.