Spectrum processd_log error messages

Products

• CA Spectrum
• DX NetOps

Issue/Introduction

In the OneClick server's $SPECROOT/lib/SDPM/processd_log, the following errors are shown:

WILL NOT START AUTORESTARTED PART NCMSERV BECAUSE WE EXCEEDED THE RETRY LIMIT!

The resultant service (in the above example - NCM) fails to start,

Seeing messages in Spectrum OneClick processd_log - WILL NOT START AUTORESTARTED PART NCMSERV BECAUSE WE EXCEEDED THE RETRY LIMIT!

Environment

DX NetOps Spectrum all releases

Resolution

These are printing because there are extra idb files that do not belong on a OneClick server. The idb files are simple text files which are used by processd to control (start, stop, restart) processes. If there are processes which would not be on a OneClick server, these exceptions would be logged in the processd_log file. By default, MYSQL.idb is the only default file.

1. Check the $SPECROOT/lib/SDPM directory for extra files, for example:
   
   NAMINGSERVICE.idb
NCMSERV.idb
    
2. For each suspect file, check to confirm whether the "Workpath" as described in the .idb file exists. For example, there is no reason that NCMSERV would be on a OneClick only platform, but you see NCMSERV.idb. Opening the NCMSERV idb file you see:
   
   APPNAME;NCM Service;
WORKPATH;$SPECROOT/NCM;
LOGNAMEPATH;$WORKPATH/NCMSERV.OUT;
    
3. Since there is no $SPECROOT/NCM on the OneClick server, you can be safely removing NCMSERV idb file which will stop the exception messages.

Additional Information

While the above example shows NCM service, this can affect any component started by processd and whose *.idb file is located under $SPECROOT/lib/SDPM/, such as LOCSERV.idb (Location Server for example).