SURUN Job failing with "No such file or directory" error on SURUN file even though SURUN file exists

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

After moving servers, and copying the $AW_HOME directory to the new server, SURUN Jobs fail with the following error

 

in SURUNP

/apps/appworx/exec/SURUNP_REQ: line 7: /apps/appworx/c/SURUN: No such file or directory

error is 127

Error code 127 indicates that SURUN could not be found in the $AW_HOME/c directory. 

After reviewing the c directory, the SURUN file does exist, has the correct permissions, and is owned by root

 

 

 

Environment

Release : 9.3

Component : APPLICATIONS MANAGER

Resolution

Redeploy SURUN from scratch:

1. Delete the file $AW_HOME/c/SURUN.

2. As the Applications Manager OS user, run the command "cp $AW_HOME/c/surun $AW_HOME/c/SURUN"

3. Without changing the permission on SURUN, rerun an SURUN Job to confirm the below error. This should indicate that SURUN is now found but does not have the correct permissions

in SURUNP
$AW_HOME/c/SURUN -user /home/anotheruser/testing/test.sh
setuid root: Operation not permitted
ERR 6 11:33:47-Unable to change uid to root.
SURUN05 - Make sure process is owned by root.

4. If the above error is seen, switch to the root User, and run the following commands to set up the correct permission on the SURUN file:

chown root $AW_HOME/c/SURUN
chmod 4711 $AW_HOME/c/SURUN

5. Rerun SURUN Job