Agent fails to start if smc and smd service name do not match
search cancel

Agent fails to start if smc and smd service name do not match

book

Article ID: 380626

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

The Linux does not start when the Service Manager is started even if the Linux Agent service is set to start automatically.

From the Service Manager log, it reads the content of the uc4.smc file but it does not start the agent.

U00022025 The file '/opt/ServiceManager/bin/uc4.smd' containing the definitions will be opened and interpreted.
U00022027 The sub-service 'AGENT-NAME' was installed.
U00022026 The command file '/opt/ServiceManager/bin/uc4.smc' containing the statements will be opened and interpreted.

Environment

Product: CA Automic Workload Automation - Automation Engine v21.x, Linux Agent v21.x

Cause

The service names in the uc4.smc and uc4.smd do not match.

 

In the uc4.smd:

DEFINE UC4 AGENT-NAME;/opt/linux/bin/ucxjlx6;/opt/automic/linux/bin/

 

In the uc4.smc:

CREATE AGENT-NAME 

Resolution

Please make sure that service names both in the uc4.smc and uc4.smd match.


In the uc4.smd:

DEFINE AGENT-NAME;/opt/linux/bin/ucxjlx6;/opt/automic/linux/bin/

 

In the uc4.smc:

CREATE AGENT-NAME