WCC UI Connectivity Issues After EC2 Rehydration or Server Migration

Products

• Autosys Workload Automation

Issue/Introduction

After rehydrating an EC2 server or performing a server migration for Autosys Workload Control Center (WCC), the WCC UI fails to connect.

Reviewing the CA-wcc.log, you may observe the following warning patterns related to the ClusterProviderDAO failing to find or add collector nodes:

WARN  #ClusterProviderDAO #(108) Check whether node exists - node [hostname], clusterport [port]WARN  #ClusterProviderDAO #(111) is collector node exists with host [hostname] and port [port]? falseWARN  #ClusterProviderDAO #(115) Lets give 5 more seconds for to get added, instancename : [hostname]

Environment

Product: Autosys Workload Automation
Component: Workload Control Center (WCC)
Version: 12.x, 24.x
Platform: Linux / AWS EC2

Cause

This issue typically occurs due to one or more of the following environmental factors:

1. Stale Database Records: The WCC database contains legacy or orphaned records in the configuration tables that point to decommissioned or older versions of WCC instances. This is especially true if the WCC had been upgraded from a previous release.
2. DNS/Hostname Resolution: The new server instance cannot correctly resolve its own hostname or the hostname of its partner nodes (in HA setups) to the correct IP address.
3. Zombie Processes: Residual WCC or Tomcat processes from previous service start attempts may be interfering with the current initialization.

Resolution

Follow these steps to remediate the connectivity issue:

1. Database Cleanup
   Identify and remove stale records from the WCC configuration tables.
   
   Warning: Back up your database before performing any manual deletions.
   Run the following SQL queries to identify current node and task configurations:
   
   

   SELECT * FROM wccadmin.CFG_COLLECTOR_NODES;
   SELECT * FROM wccadmin.CFG_COLLECTOR_TASKS;

   
   If records exist that point to old hostnames or legacy versions (e.g., versions no longer in use like 12.1.01), work with your DBA to delete those specific rows.
   
   
2. Update Local Hosts File
   Ensure that the local /etc/hosts file on the WCC server contains explicit entries for the local hostname and IP, as well as any cluster partner nodes.
   
   

   Example entry:

   ###.###.###.###   mywcc-server.example.com   mywcc-server

3. Clear Residual Processes
   Before restarting services, ensure no stale WCC processes are running:

   • Stop WCC services: unisrvcntr stop CA-wcc

   • Check for residual Java or WCC processes: ps -ef | grep wcc

   • Kill any remaining processes: kill -9 [PID]

4. Restart Services
   Start the WCC services and monitor the logs:

   • Start services: unisrvcntr start CA-wcc

   • Tail the log to confirm the node is added successfully: tail -f CA-wcc.log

Additional Information

To stay updated on fix statuses, subscribe to this article.
To speak with a customer representative or a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on your respective region.