After OS Patching and Reboot, WCC Server does not validate AutoSys "E190099 ### - Connection exception encountered. CAUAJM_E_00020 Local error in attempt to send request. RC=1."

Products

• Autosys Workload Automation

Issue/Introduction

• After performing Linux OS patching and rebooting the WCC server, the Primary WCC instance becomes inaccessible, although services appear to start.
• Users can login to the primary server, but are unable to see jobs nor validate AutoSys configuration on the Primary WCC instance.
• The Secondary WCC server remains operational.

During validation, the WCC logs may show connection exceptions or errors like below:
    E190099 ### - Connection exception encountered. CAUAJM_E_00020 Local error in attempt to send request. RC=1.
    E190099 ### (monitoring id validation) - Connection exception encountered. CAUAJM_E_00020 Local error in attempt to send request. RC=1.

 

Application Server logs show that the connections from WCC server are getting established, but nothing more happens. It just shows connections established in a loop.

Cause

The /etc/hosts file on the affected WCC server was modified or reverted during the OS patching process, resulting in missing or incorrect entries. The WCC instance could not resolve the required application server hostnames (IP address, short name, and FQDN) to communicate with the environment, leading to connectivity failures.

Resolution

1. Compare the /etc/hosts file of the functional WCC node with the /etc/hosts file on the problematic node.
2. Update the /etc/hosts file on the problematic WCC node to include the missing entries for all application servers. Ensure that each entry contains the IP address, short name, and Fully Qualified Domain Name (FQDN).
3. Once the entries are added, restart the WCC services to apply the configuration: unisrvcntr stop CA-wcc-services unisrvcntr start CA-wcc-services
4. Verify connectivity by attempting to access the WCC Web UI or performing a network test (e.g., ping or curl) to the application servers from the affected WCC node.