The unisrvcntr command fails to start AutoSys services, yet the /etc/init.d/waae* start up scripts are able to start AutoSys successfully.

book

Article ID: 221967

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys)

Issue/Introduction

Trying to start the AutoSys services via the unisrvcntr command fails with this output:

(example trying to start the Application Server for an instance named ACE)

$ unisrvcntr start waae_server.ACE
Starting waae_server.ACE (via systemctl):  Job for waae_server.A12.service failed because the control process exited with error code. See "systemctl status waae_server.ACE.service" and "journalctl -xe" for details.
                                                           [FAILED]
Executed waae_server.ACE start...................................FAIL 1


In the system's /var/log/messages log you may see something like:

Jul 15 12:25:15 <hostname> systemd[1]: Starting LSB: AutoSys Workload Automation Application Server...
Jul 15 12:25:15 <hostname> waae_server.<instance>[2509538]: <install_path>/CA/SharedComponents/Csam/SockAdapter/scripts/csamsetlibpath.sh: line 2: <install_path>/CA/SharedComponents/Csam/SockAdapter/scripts/csamgetarch: Permission denied
Jul 15 12:25:15 <hostname> waae_server.<instance>[2509538]: WAAE Application Server (<instance>) /etc/rc.d/init.d/waae_server.<instance>: line 125: <install_path>/CA/WorkloadAutomationAE/autosys/bin/as_server: Permission denied
Jul 15 12:25:15 <hostname> waae_server.<instance>[2509538]: /etc/rc.d/init.d/waae_server.<instance>: line 125: exec: <install_path>/CA/WorkloadAutomationAE/autosys/bin/as_server: cannot execute: Permission denied
Jul 15 12:25:20 <hostname> waae_server.<instance>[2509538]: [FAILED]
Jul 15 12:25:20 <hostname> systemd[1]: waae_server.<instance>.service: Control process exited, code=exited status=1
Jul 15 12:25:20 <hostname> systemd[1]: waae_server.<instance>.service: Failed with result 'exit-code'.
Jul 15 12:25:20 <hostname> systemd[1]: Failed to start LSB: AutoSys Workload Automation Application Server.
Jul 15 12:25:20 <hostname> assrvc[2509523]: Executed waae_server.<instance> start...................................FAIL 1

The issue persists with unisrvcntr despite:

Successfully start the services using the /etc/init.d/waae* startup scripts

-rwxr-xr-x.  1 root root  6485 Jun 11  2020 waae_sched.ACE
-rwxr-xr-x.  1 root root  6283 Jun 11  2020 waae_server.ACE

Verifying the files under $AUTOSYS/bin have correct permissions

-rwxr-xr-x.  1 autosys autosys  267048 Jun  8  2020 as_server
-rwxr-xr-x.  1 autosys autosys 3149344 Jun  8  2020 event_demon

Confirming the $AUTOSYS/csutils/bin/assrvc file has root ownership and the setuid bit:

-rwsr-xr-x. 1 root root 123112 Jun  8  2020 assrvc

 

Cause

This has been known to occur if SELinux is enabled and contains a policy preventing the user switch when the unisrvcntr command executes $AUTOSYS/csutils/bin/assrvc with the setuid bit.

Environment

CA AutoSys Workload Automation 12.x

Resolution

Check if SELinux is enabled with command 'sestatus'.

Try disabling it temporarily in the 'etc/selinux/config' file as mentioned in this link:
https://access.redhat.com/solutions/3176

The unisrvcntr command will work, confirming it is an SELinux policy issue.

Consult your system admins about disabling SELinux or removing the blocking policy.