unix agent 12.3.2 crash / could not be started properly

book

Article ID: 196568

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation CA Automic Operations Manager CA Automic Oracle

Issue/Introduction

If an agent is stopped while Jobs are still running, it may happen that it won't start afterward.
The logs show :

20200615/193144.793 - U00011175 Negative JOB_INF was sent from Agent 'OS_EXAOGDPP.AG'. Job name '[email protected]@RUNSASLOAD.CUSTOMER_RELEVANCE.JOB' (RunID '0009847254'), old job status 'Active', new job status 'Active'
20200615/193144.839 - U00011175 Negative JOB_INF was sent from Agent 'OS_EXAOGDPP.AG'. Job name '[email protected]@RUNCALCULATION.EXPOSURE_1.JOB' (RunID '0009838260'), old job status 'Active', new job status 'Active'

Cause

Jobs can't move correctly in "Lost" status and are stuck.
They will prevent the Agent from starting as expected.

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

Workaround :

Restart the agent until the jobs get in "LOST" status.
If they don't do so, remove the corresponding job logs on the server and restart the agent again.

 

Fix : 

12.3.3 (available)