Autosys agent did not come up after reboot

book

Article ID: 195254

calendar_today

Updated On:

Products

CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation Agent CA Workload Automation AE

Issue/Introduction

Autosys agent on linux did not come up after reboot. The Agent service did not start.


Environment

Release : 11.4

Component : CA Workload Automation System Agent

Resolution

The encountered problem with the Agent not starting at reboot is most often related to the required System Resources Not being Available at that rime.

You can find the information about the Agent Startup issues in “nohup.stdout” and “nohup.stderr” files available under the Agent installation directory.

Example:

# cd /opt/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT

# ls –al

....

-rw-r--r--. 1 root root 0 Jul 12 03:56 nohup.stderr

-rw-r--r--. 1 root root 0 Jul 12 03:56 nohup.stdout



The “nohup.stdout” and “nohup.stderr” files are overwritten each time you restart the Agent.

When Agent has been started successfully, these files are empty because there is not any errors to report.

So in your environment these files are probably empty at this time if you have restarted the Agent.

In case problem persisted in future, we recommend you to take a backup of “nohup.stdout” and “nohup.stderr” for further investigation before restarting the Agent.