How to configure Spectrum to automatically start the SpectroSERVER and Archive Manager when the system is restarted.

Products

• Spectrum
• Network Observability

Issue/Introduction

How to configure Spectrum to automatically start the SpectroSERVER and Archive Manager when the system is restarted.

How can the SS and ArchMgr be autostarted after reboot?

Environment

Release: Any
Component: processd

Resolution

This can be accomplished by modifying the $SPECROOT/lib/SDPM/partslist/SS.idb and ARCHMGR.idb files and un-commenting the AUTOBOOTSTART parameter and setting the value to "y".

Example:

# Processd Install Ticket for SPECTRUM Archive Manager.
PARTNAME;ARCHMGR;
APPNAME;SPECTRUM Archive Manager;
WORKPATH;$SPECROOT/SS/DDM;
LOGNAMEPATH;$WORKPATH/ARCHMGR.OUT;
LOGBACKUPMAX;10;
ADMINPRIVS;y;
#AUTORESTART;N;
AUTOBOOTSTART;Y;
#STATEBASED;N;
NUMPROCS;1; // one per host
RETRYTIMEOUT;0; // seconds
#TICKETUSER;
RETRYMAX;0;     // retries
STARTPRIORITY;30;
SERVERPROCESS;Y;
#SERVICE;N;
#ENV;<var>=<value>;
ARGV;$SPECROOT/SS/DDM/ArchMgr<CSEXE>; //

NOTE: Do not change AUTORESTART;N; in the SS.idb or ARCHMGR.idb files to "y". The reason being is if the SS or ArchMgr crash, it will not remove the .VNMDB.LOCK or .DDMDB.LOCK files preventing the SS and ArchMgr from starting. Always assume database corruption in the event of a crash.

After making the change to the idb files, you will need to restart processd to pick up the change.

Shutdown the SpectroSERVER and ArchMgr gracefully before restarting processd:

- Log into the system as the user that owns the Spectrum installation

- If on Windows, start a bash shell by running "bash -login"

- cd to the $SPECROOT/bin directory and enter the following command to shutdown the SpectroSERVER and ArchMgr:

./stopSS.pl

Then stop processd:

systemctl stop processd

restart processd:

systemctl start processd

The SS and ArchMgr will automatically start now since the AUTBOOTSTART was changed to Y

Additional Information

Please reference the "Install Ticket Files" section of the documentation for more information.

If you are using Linux, you will need to uncomment TICKETUSER as well:

• TICKETUSER

   

  Defines the username of the user who is authorized to run the process when the AUTOBOOTSTART and/or AUTORESTART fields are set. This field is only required when those fields are included in the install ticket. This field is not applicable on Windows because all processes run as the processd install user.