Linux delayed startup after sysedge install

Document ID : KB000004242
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

It has been observed in some cases that after installing sysedge or other CA Products that utilize the CA-CCS package that on some flavors of Linux, that system restart (reboot) becomes delayed taking an additional 15 to 20 minutes at times.

In some cases, even if the delays aren't seen, some errors may show up during the boot sequence:

[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-ais.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-alert.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-atech.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-cal.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-cal.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-cam.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-cauwvdmn.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-cci.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-diadna.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-diaukb.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-discovery .service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-em.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-emsrvc.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-has.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-help.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-mcc.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-opr.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-snmp.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-star.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-tomcat.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-wvubi.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +CA-wvmgr.service, ignoring: Invalid argument
[ 123.456789] systemd[1]: [/etc/rc.d/init.d/CA-CCS:29] Failed to add dependency on +postgres.service, ignoring: Invalid argument
Environment:
Red Hat 7.x and/or other supported Linux platforms that use systemd.
Cause:

Some versions of systemd do not appear to handle backwards compatibility with LSB Style init scripts.

/etc/init.d/CA-CCS script contains the line:

# Required-Start: +CA-ais +CA-alert +CA-atech +CA-cal +CA-cam +CA-cauwvdmn +CA-cci +CA-diadna +CA-diaukb +CA-discovery +CA-em +CA-emsrvc +CA-has +CA-help +CA-mcc +CA-opr +CA-snmp +CA-star +CA-tomcat +CA-wvubi +CA-wvmgr +postgres

# is a comment but Required-Start is an OS chkconfig / init parameter and when encountered the system treats the services in required start as a dependency.

The "+" (plus sign) means its optional. If the services exist (which in most cases these services do not), start them, otherwise ignore them:
"Names starting with a '+' sign are marked as optional. If the service with the name after the plus sign is available it will be used, if not available it is ignored silently."

Some Linux Distributions running systemd (as opposed to init) are not treating "+" parameters as optional (even though they are backwards compatible with init style scripts). Systemd then tries to start each optional component and waits until the start times out.

Resolution:

For CA-SystemEDGE systems not running in managed mode (meaning not being configured by VAIM or controlled by CA-Virtual Assurance), the installation can be done with CASE_LEGACY_MODE="yes". Legacy Mode does not install cam which is the component that installs the CA-CCS script in question.

If VAIM is being used to manage SystemEDGE agents, or for systems that were already installed without the Legacy Mode parameter, the CA-CCS Script can be safely removed or the above #Required-Start and #Required-Stop lines can be removed from the /etc/init.d/CA-CCS script. Once either of those changes have been made, the delay and/or errors will no longer be observed on future reboots.