Spectrum's "processd --start" no longer automatically starts upon reboot with RHEL 7.9

book

Article ID: 205668

calendar_today

Updated On:

Products

CA Spectrum CA eHealth

Issue/Introduction

We are running NetOps 20.2.3  in a distributed RHEL 7 environment.  Recently, our RHEL servers were patched and rebooted so that the version went from 7.8 to 7.9 (as per /etc/redhat-release, which says "Red Hat Enterprise Linux Server release 7.9 (Maipo)").  Ever since then, whenever the Spectrum servers are rebooted, <$SPECTRUM_HOME>/lib/SDPM/processd --start no longer runs.  We have to login to the server and manually start that process using our sudo accounts.

 

Environment

Release : 20.2

Component : Spectrum Core / SpectroSERVER

Resolution

Since the latest RHEL versions doesn't support init system(/etc/init.d) and Linux introduced the concept of systemd units. All of Spectrum init scripts were converted to systemd service units to ensure that all Spectrum applications are started smoothly during reboot time. We found a known limitation in RHEL that in case if processd manually started and stopped with <$SPECROOT>/lib/SDPM/processd ---start or <$SPECROOT>/lib/SDPM/processd--stop 

then Linux systemd doesn't get any notification regarding the processd status in order to stop/start processd daemon during reboot time.

Engineer request to use always "systemctl" to control the start/stop processd daemon

/usr/bin/systemctl stop processd

/usr/bin/systemctl start processd