Jobs get stuck in starting

Products

• Workload Automation Agent

Issue/Introduction

Issue/Problem/Symptoms: 

Jobs get stuck in STARTING. Jobs are being submitted to the System Agent and the Agent executes the job but the job status remains as STARTING.  The transmitter.log does not show any entries indicating any communications back to the AutoSys Scheduler.

Environment:  

System Agent 11.3x, Unix Linux

Cause:

This can happen if the message queue file is deleted while the agent is running. The message queue is created with a key that is based upon the inode number of the message queue file. The system uses that number and generates the msqid, which is the unique id for the message queue.  The runner_os_component.log will show what file is used for the message queue file when the agent is started.

Resolution:

By default the message queue file is cybAgent.bin. However you can optionally choose to use a different file by setting oscomponent.msgqueue=<filename> in the agentparm.txt file. To resolve if the message queue file is deleted and you did not use the default, restart the agent.

 

 

 

Environment

Release: WKLASE99000-11.3-Workload Automation-Agent SE
Component: