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

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


Article ID: 205668


Updated On:


CA Spectrum CA eHealth


We are running NetOps 20.2.x  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.



Release : 20.2

Component : Spectrum Core / SpectroSERVER


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.

Do not use the processd.pl or processd application in the $SPECROOT/lib/SDPM directory anymore.  Processd has been moved to system units.  From now on you should stop and start processd using systemclt:

/usr/bin/systemctl stop processd

/usr/bin/systemctl start processd