Unable to start agent after system migration
search cancel

Unable to start agent after system migration

book

Article ID: 207199

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

When attempting to start the Automic solution with Service Manager not all of our agents are starting:

20210124/163330.373 - -------------------------------------------------------------------------------------
20210124/163330.373 - U00022044 Real user '<uid>' and effective user '<uid>'.
20210124/163330.404 - U00022025 The file '<path to ucy.smd>' containing the definitions will be opened and interpreted.
20210124/163330.404 - U00022027 The sub-service 'UC4 Unix-Agent' was installed.
20210124/163330.404 - U00022027 The sub-service 'UC4-RMS' was installed.
20210124/163330.404 - U00022026 The command file '<path to uc4.smc>' containing the statements will be opened and interpreted.
20210124/163330.404 - U00022035 Process 'UC4 Unix-Agent' will be started in '0' seconds.
20210124/163330.405 - U00022035 Process 'UC4-RMS' will be started in '5' seconds.
20210124/163330.435 - U00022032 'TCP' socket with port '8871' successfully created.
20210124/163330.436 - U00022032 'UDP' socket with port '8871' successfully created.


 

 

Environment

Release : 12.3.x

Component : AUTOMATION ENGINE

Cause

Unix Permissions

Resolution

The Automic Admin was starting the Service Manager with a non-root user.

The particular agent in question 'UC4 Unix-Agent' was owned by root and a group that the non-root user was not a member of.

Once we added the Service Manager account to the group that owned our Unix Agent -> everything started fine.