Non-root owned AutoSys jobs stuck in STARTING on Linux
search cancel

Non-root owned AutoSys jobs stuck in STARTING on Linux

book

Article ID: 448242

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

Jobs assigned to non-root job owners are getting stuck in the STARTING status. The AutoSys System Agent executes the command, but fails to send back status details for non-root owned jobs.

The following error is logged in the job spool log files:

cybspawn: unable to obtain the message queue ID. errno:13 Reason:Permission denied

 

Environment

Operating System: Linux

Product Release/Version: AutoSys 12.x or 24.x

Cause

Stale IPC message queues allocated to the root user or another process remain active in the operating system memory. When cybspawn attempts to access or allocate the message queue under the non-root user context, permission is denied (errno:13).

Resolution

 

  • Stop the AutoSys System Agent service.

  • Display all system IPC message queues and process IDs:

    ipcs -q
    ipcs -q -p
    
  • Identify and remove any orphan message queues that remain allocated while the agent is down:

    ipcrm -Q <msgkey>
    
  • Restart the AutoSys System Agent service and verify job execution.

 

 

 

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.