After RHEL Server reboot, the AutoSys agent is not starting Automatically.
search cancel

After RHEL Server reboot, the AutoSys agent is not starting Automatically.

book

Article ID: 403844

calendar_today

Updated On:

Products

Autosys Workload Automation Workload Automation Agent

Issue/Introduction

I am seeing the following error while the system tries to restart the agent after reboot.

[<USER>@<HOSTNAME> etc]# systemctl status waae_agent-WA_AGENT.service
× waae_agent-WA_AGENT.service - LSB: Workload Automation System Agent
     Loaded: loaded (/etc/rc.d/init.d/waae_agent-WA_AGENT; generated)
     Active: failed (Result: exit-code) since Tue 2025-07-01 11:06:35 PDT; 6min ago
       Docs: man:systemd-sysv-generator(8)
        CPU: 2ms

Jul 01 11:06:35 <HOSTNAME> systemd[1]: Starting LSB: Workload Automation System Agent...
Jul 01 11:06:35 <HOSTNAME> waae_agent-WA_AGENT[1506]: /etc/rc.d/init.d/waae_agent-WA_AGENT: line 39: /etc/profile.CA: Permission denied
Jul 01 11:06:35 <HOSTNAME> systemd[1]: waae_agent-WA_AGENT.service: Control process exited, code=exited, status=1/FAILURE
Jul 01 11:06:35 <HOSTNAME> systemd[1]: waae_agent-WA_AGENT.service: Failed with result 'exit-code'.
Jul 01 11:06:35 <HOSTNAME>systemd[1]: Failed to start LSB: Workload Automation System Agent.

 

Environment

AutoSys System Agent 12.x
RHEL

Cause

Issue with SELinux

Resolution

The issue was resolved by configuring SELinux to allow access to the profile.CA.