search cancel

Is there a way to ensure a graceful shutdown of Spectrum or processes before a reboot?

book

Article ID: 202129

calendar_today

Updated On:

Products

CA Spectrum DX NetOps

Issue/Introduction

There are occasions when a processd shutdown cannot shutdown processes under its control.

If these processes where started with priority > 20, then when processd stops, processes at a priority 20 or less are still running, so when a server is rebooted these processes aren't shutdown cleanly (ie SSdb gets corrupted). An example is an AlarmNotifier, where it failed to shutdown because one of its child processes (set/update/clear script) has hung.

Is there a way to tell processd to force kill specific processes or is there a mechanism within AlarmNotifier to disown/un-associate child/spawned processes so processd can stop AlarmNotifier's and therefore cleanly shutdown SS?

Environment

Release : All Supported Releases

Component : SPCCSS - Spectrum Core / SpectroSERVER

Resolution

If you are experiencing hangs using processd to bring down the SS you can manually shutdown Archive Manager and SS using cmdC before attempting to stop processd for a Server Reboot. From $SPECROOT/bin, run:

./cmdC localhost 2 ARCHMGR

THEN

./cmdC localhost 2 SS

To stop MySQL:

./cmdC localhost 2 MYSQL