Engine Instances are failing after rebooting the ITCM domain manager . Need to start every instance manually from command line .

book

Article ID: 5938

calendar_today

Updated On:

Products

CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager

Issue/Introduction

Engine Instances are failing after rebooting the ITCM domain manager . Need to start every instance manually from command line . 

caf status shows. 

These DSM services auto-start but are currently stopped:

[1]  Engine (SystemEngine)

[2]  Engine (Groups_Evaluation_&_Reports)

[3]  Engine (IsolationEngine)

 

 

Cause

some cases , the services related to database will take time to start after rebooting the server . ITCM Engines will fail to make connections to MDB duel to database services delay. 

Environment

ITCM Domain Manager.

Resolution

Run the below command on domain manager machine where engines instance are present to set a delay in caf startup after system reboot. 

ccnfcmda -cmd setparametervalue -ps itrm/common/caf/general -pn startup_delay -v 10 

To check whether above command has set the correct value, use the below command. It should give value as 10. 

ccnfcmda -cmd getparametervalue -ps itrm/common/caf/general -pn startup_delay 

This command will introduce a delay of ten minutes in caf startup after system reboot. Engine starts are failing because they are not able to establish 'database connection' may be because database services are coming up after sometime of reboot.

Now check the problem after next reboot . Open a issue with CA if above solution not resolved the problem.