Duplicate alarmNotifier applications spawned after SpectroSERVER restart.

Products

• Network Observability
• Spectrum

Issue/Introduction

You run a customized alarmNotifier with custom application name, using named policies and schedules.  After a SpectroSERVER reboot you see a second AlarmNotifier application using the default policy.

Cause

/Spectrum/lib/SDPM/partslist/ALARMNOTIFIER.idb was configured to be started by processd on OS reboot.

# Processd Install Ticket for AlarmNotifier
PARTNAME;ALARMNOTIFIER;
APPNAME;AlarmNotifier;
WORKPATH;$SPECROOT/Notifier;
LOGNAMEPATH;$WORKPATH/NOTIFIER.OUT;
#ADMINPRIVS;N;
AUTORESTART;y;
AUTOBOOTSTART;y;
#STATEBASED;N;
NUMPROCS;1; // one per host
RETRYTIMEOUT;600; // 10 minutes
TICKETUSER;spectrum;
RETRYMAX;3;     // 3 retries allowed
STARTPRIORITY;30;
SERVERPROCESS;Y;
#ENV;<var>=<value>;
ARGV;$SPECROOT/Notifier/AlarmNotifier<CSEXE>;

 

It was then copied to run a non default alarmNotifier.  The original renamed expecting that this would stop it from running, similar to renaming an executable so that it cannot be called via a script.   But this does not stop it from being run. 

 

Resolution

Autoboot start should be turned off in the idb file.  

AUTOBOOTSTART;n;

Or the unwanted idb should be moved out side of the partslist folder. 

Additional Information

How to run multiple or custom alarmNotifiers