After upgrade of Linux from Redhat 7 to 8, Autosys startup gives "as_server: error while loading shared libraries: libapicom.so: cannot open shared object file: No such file or directory"

Products

• Autosys Workload Automation

Issue/Introduction

Autosys server processes do not start and command line programs gives errors like below, after operating system was upgraded from RHEL 7 to 8:

waae_server.DEV start  
WAAE Application Server (DEV) as_server: error while loading shared libraries: libapicom.so: cannot open shared object file: No such file or directory
                                                           [FAILED]

waae_sched.DEV restart 
WAAE Scheduler (DEV) stopped.

Scheduler started.
event_demon: error while loading shared libraries: libascmn.so: cannot open shared object file: No such file or directory
                                                           [FAILED]

autoflags -a

/opt/CA/WorkloadAutomationAE/autosys/bin/autoflags: error while loading shared libraries: libascmn.so: cannot open shared object file: No such file or directory

Environment

Autosys 12.x on Linux

Cause

 

- fapolicyd was what was blocking AutoSys from using its shared libraries.  This is a software that controls execution of applications based on a user-defined policy and was part of security compliance.

- Make sure to look for FAPOLICY as well as FANOTIFY  in /var/log/audit based system audit logs

- FAPOLICY trust database was not generated correctly when it was installed upon upgrading from RHEL 7 to RHEL 8.

Resolution

Normally one can just add the libraries directory to fapolicyd's allow rules to fix it. 

 

Otherwise a waiver needs to be submitted to disable fapolicyd and then restart/reuse Autosys