After an upgrade the Cluster Server (VCS) HAD daemon does not start.

book

Article ID: 100022721

calendar_today

Updated On:

Resolution

After an upgrade it was observed that the HAD daemon did not start:
 
2010/03/22 23:47:00 VCS NOTICE V-16-1-10322 System xxxxxxxx (Node '0') changed state from LOCAL_BUILD to RUNNING
2010/03/22 23:47:00 VCS ERROR V-16-1-10391 System 'xxxxxxxx' listed in main.cf but absent in LLT config file
2010/03/22 23:47:00 VCS ERROR V-16-1-10068 System xxxxxxxx - VCS engine will exit to prevent any inconsistency. Please review names of systems listed in VCS configuration and make sure they are present and node ids are consistent in LLT configuration files on all systems in the cluster
 
Check /etc/llttab, /etc/llthosts, /etc/VRTSvcs/conf/sysname and /etc/VRTSvcs/conf/config/main.cf for any inconsistencies in naming conventions across the nodes in the cluster.
This incident related to use of a fully-qualified domain name being used in all files except the main.cf file.
 
Once node names are again consistent, attempt to restart the HAD daemon.
 
 

 

Issue/Introduction

After an upgrade the Cluster Server (VCS) had daemon does not start.
Powered by Wolken Software