Communication check between the CA Workload Automation AE Agent and Application Server error CAUAJM_E

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent

Issue/Introduction

Communication check between the CA Workload Automation Agent and the Application Server fails with the following error.

#autoping -M agent -S
CAUAJM_I_50023 AutoPinging Machine [agent]
CAUAJM_I_50031 Checking the Agent's connectivity to the Application Server.
CAUAJM_E_50037 ERROR: Agent failed to communicate with Application Server.
CAUAJM_E_50041 ERROR: Agent returned <Error loading support library - "libas_c_bind.so: cannot open shared object file: No such file or directory">.
CAUAJM_E_50281 AutoPing from the Scheduler WAS NOT SUCCESSFUL.

CAUAJM_E_50037 ERROR: Agent failed to communicate with Application Server.
CAUAJM_E_50041 ERROR: Agent returned <Error loading support library - "libas_c_bind.so: cannot open shared object file: No such file or directory">.
CAUAJM_E_50283 AutoPing from the Application Server WAS NOT SUCCESSFUL.

CAUAJM_E_50026 ERROR: AutoPing WAS NOT SUCCESSFUL.

This is not a problem for normal job processing on the agent.
However, the special type of operations such as jobs having Binary Large Objects (BLOBs) where the application server communication is needed would fail.

Environment

CA Workload Automation AE 11.3.5 and 11.3.6 +

Cause

CA Workload Automation AE Agent version and it's binary architecture compatibility.
The x64 bit architecture of the CA WA Agent 11.3+ versions will not be able to communicate with the CA Workload Automation AE Application Server

Resolution

The CA Workload Automation AE Agent needs to be upgraded to version 11.4. Starting from System Agent 11.4 the agent binary architecture x64bit has been enhanced to work with the Application Server.
If the agent is already at version 11.4, ensure the Agent startup script "<AGENT_INSTALL_DIR>/cybAgent" does contain the source path for the library "libas_c_bind.so". Example file:


#cat /opt/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT/cybAgent
    #!/bin/sh
    #
    # cybAgent for linux-x86-64
    #
    #
    # Copyright (c) 2018 CA. All rights reserved.
    #
    # Script to run the WA Agent
    #
    #
    EWA_SHARED=/opt/CA/SharedComponents
    export EWA_SHARED
    ETPKIHOME=$EWA_SHARED/ETPKI
    export ETPKIHOME
    CAPKIHOME=$EWA_SHARED/CAPKI
    export CAPKIHOME
    CSAM_SOCKADAPTER=$EWA_SHARED/Csam/SockAdapter
    export CSAM_SOCKADAPTER
        LD_LIBRARY_PATH="/opt/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT:/opt/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT/jre/lib/amd64/server:/opt/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT/jre/lib/amd64:$ETPKIHOME/lib:$CSAM_SOCKADAPTER/lib:$CSAM_SOCKADAPTER/lib64:/opt/CA/WorkloadAutomationAE/autosys/lib:$LD_LIBRARY_PATH"
    export LD_LIBRARY_PATH

    cd '/opt/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT'
    exec ./cybAgent.bin "$@"

If the Agent version can not be upgraded due to infrastructure restrictions, the x32bit binary is available for all the CAWA Agent 11.3+ versions. Which can be downloaded from support portal to replace the existing x64bit binary (uninstall existing x64bit and install x32bit).

A successful autoping communication test between the agent and application server returns the following.


# autoping -M agent -S
CAUAJM_I_50023 AutoPinging Machine [agent]
CAUAJM_I_50031 Checking the Agent's connectivity to the Application Server.
CAUAJM_I_50025 AutoPing WAS SUCCESSFUL.

Additional Information

autoping Command—Verify Server, Agent, and Client Communication
Manage Binary Large Objects (Blobs)
CA WAAE requirements to Communicate with AE Clients and CA WA system agents
CA Workload Automation AE Agent -System Requirements and Supported Platforms