After upgrading WCC from 12.0 to 12.0.1, WCC does not start anymore
search cancel

After upgrading WCC from 12.0 to 12.0.1, WCC does not start anymore

book

Article ID: 208213

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

Getting the following error repeatedly in the CA-wcc.log


INFO   | jvm 1    | 2021/01/13 10:06:09 |        8 | @tomcat-resource <WrapperStartStopAppMain> []  WARN #ClusterProviderDAO                 # Lets give 5 seconds for <default-collector> to get added, instancename : <WCC-Real-Hostname>
INFO   | jvm 1    | 2021/01/13 10:06:14 |       13 | @tomcat-resource <WrapperStartStopAppMain> []  WARN #ClusterProviderDAO                 # Wait complete, check for <default-collector> node existance
INFO   | jvm 1    | 2021/01/13 10:06:14 |       13 | @tomcat-resource <WrapperStartStopAppMain> []  WARN #ClusterProviderDAO                 # Check whether <default-collector> node exists - node <WCC-Real-Hostname>, clusterport 7004
INFO   | jvm 1    | 2021/01/13 10:06:14 |       13 | @tomcat-resource <WrapperStartStopAppMain> []  WARN #ClusterProviderDAO                 # is collector node exists with host <WCC-Real-Hostname>and port 7004? false
I

Environment

Release : 12

Component : CA Workload Automation AE (AutoSys)

Cause

WCC's /opt/CA/WorkloadAutomationAE/wcc/data/config/application/config/resources/connection.properties has a HA node value which does not correspond to the entries in the WCC database table cfg_ha_instance.nodename

It has to match the exact value 

Resolution

1) Backup /opt/CA/WorkloadAutomationAE/wcc/data/config/application/config/resources/connection.properties file first 

2) Edit the connection.properties and set the  ha.node   to the same exact value as the associated cfg_ha_instance.nodename  value

3) Restart WCC

Additional Information

If needed, you can consider this approach too:

-- identify if there are any other WCC collector hosts that are not valid anymore  

select * from  cfg_collector_nodes

 

--  on the old hosts, identify what the node_id records are where collector tasks are still present. Example : node_id  1, 21 and 41  were the old ones

select * from cfg_collector_tasks   

 

-- delete records from cfg_collector_tasks for the old invalid nodes

delete from cfg_collector_tasks where node_id=1;

commit;

-- delete records from cfg_collector_nodes with invalid nodes

delete from cfg_collector_nodes where node_id=1;

delete from cfg_collector_nodes where node_id=21;

delete from cfg_collector_nodes where node_id=41;

commit;

 

- Restart WCC.