Jobs fail to execute when the Control-M/Agent is running in Non-Root mode.

The Control-M/Agent and Control-M/Server logs in <ctm_home>/proclog may show messages similar to: Job Failed due to user environment.

Job Sysout may show: Job aborted due to error executing '<path to agent/ctm/exe/vault/su_bmc'

This message can have the following causes:
    1.  PAM may not be configured properly on this host.
    2.  su_bmc under exe/vault is not set with the "sticky bit" as root.
 

Legacy ID:KA350717
For the PAM issue:

1. Contact the local System Administrator for assistance in determining if the host uses PAM.
2. If using PAM, ask the System Administrator to force the agent to bypass PAM and use the local 'passwd' or 'shadow' file.
3. If not using PAM, disable it in the Control-M Configuration Manager (CCM) by selecting the Agent and then choosing Agent System Parameters and setting "ENABLE_PAM"=N.

For the su_bmc issue:

Make sure the sticky bit is set for su_bmc.
An ls -al command should show the following permissions for su_bmc:
-rwsrwxr-x 1 root domain users 41346 Jan  8  2018 su_bmc

Note the s.  If the s is an r in the permission above, please perform the following:

1.  Logon to the Control-M/Agent as root.
 
2.   Navigate to where the set_agent_mode script is ( <install path>/ctm/scripts ).
 
3.   Issue command :
./set_agent_mode
 
At the Enter Control-M/Agent UNIX username prompt, just hit Enter.
 
4.   Select option 2 - Enable root mode.   Respond with Y when prompted for restart.
 
5.   Issue ./set_agent_mode again
At the Enter Control-M/Agent UNIX username prompt, just hit Enter.
 
6.   Select option 1 - Enable non-root mode.   Respond with Y when prompted for restart.
7.   Check the sticky bit of exe/vault/su_bmc
 
If it is still not "s", please send us the all the files in the proclog directory.

In addition, check the mount options for the device the Control-M/Agent home directory is on.
Make sure that it is not mounted with the "nosuid" flag, which prevents the sticky bit from taking effect.