Job is stuck in STARTING status
search cancel

Job is stuck in STARTING status

book

Article ID: 93645

calendar_today

Updated On:

Products

Workload Automation Agent

Issue/Introduction

Jobs go to STARTING state and not running.

The agent is online and responds to autoping requests.

However job executions on the agent is not returning the RUNNING or SUCCESS event.

On the Agent server, the transmitter logs do not reflect any messages related to the jobs execution.

Environment

Agent Release: ANY

Cause

The following errors are noted in the spool file for the impacted job(s)

[/app/autosys/r24/SystemAgent/WA_AGENT/spool/SIT_SCH/MAIN/WAAE_WF0.1/1111111.22222222_1.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.joblog] can not be opened: [Permission denied]. The message is: <09/23/2025 09:45:32.252-0400 CAWA_I_20009 User and group identity successfully set for user

[/app/autosys/r24/SystemAgent/WA_AGENT/spool/SIT_SCH/MAIN/WAAE_WF0.1/1111111.22222222_1.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.joblog] can not be opened: [Permission denied]. The message is: <09/23/2025 09:45:32.252-0400 CAWA_I_20009 Recheck access permissions with new uid

[/app/autosys/r24/SystemAgent/WA_AGENT/spool/SIT_SCH/MAIN/WAAE_WF0.1/1111111.22222222_1.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX_wrapper.sh': error 13 (Permission denied)Log file [/app/autosys/r24/SystemAgent/WA_AGENT/spool/SIT_SCH/MAIN/WAAE_WF0.1/1111111.22222222_1.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.joblog] can not be opened: [Permission denied]. The message is: <09/23/2025 09:45:32.252-0400 CAWA_E_20050 Shell verification failed. Error code: 4014
>
cybspawn: unable to obtain the message queue ID. errno:13 Reason:Permission denied

 

Resolution

The above messages indicate that the userid defined in the job does not have the correct permissions to access the agent directory/subdirectories.

Follow the below procedure to validate permissions of the user.

  • su as the user acount that is the owner of the job.
  • Then attempt to cd to the agent installation directory. (default location /opt/CA/WorkloadAutomationAE/SystemAgent)
    You may receive a permission denied message, as that userid.
  • If so, then the next step is to engage the System Administrator to resolve the permission problem by recursively changing the permission to rwxr-x-r-x (chmod 755) to the /opt/CA/WorkloadAutomationAE/SystemAgent directory.

After the permission change, you should able to run the job to completion and receive all the statuses.

Note: An agent restart is not required.

Powered by Wolken Software