Having trouble with getting VCS 'had' to start.
Created: 13 Nov 2012 • Updated: 14 Nov 2012 | 7 comments
This issue has been solved. See solution.
I installed VCS 6.0.2 on RHEL 6.1, chose not to start LLT and GAB during configuration so that it would be configured a single node cluster in a standalone cluster.
However 'had' failed to startup, and the error message at the end of installation was as follows :
"It is likely that the startup failure issues will be resolved after rebooting the system. If issues persist after reboot, contact Symantec technical support or refer to installation guide for further troubleshooting."
I restarted the system, but unfortunately 'had' still would not start after running 'hastart'.
The file /var/VRTSvcs/log/engine_A.log does indicate that 'had' started :
2012/11/13 21:24:27 VCS NOTICE V-16-1-11022 VCS engine (had) started
2012/11/13 21:24:27 VCS NOTICE V-16-1-11050 VCS engine version=6.0
2012/11/13 21:24:27 VCS NOTICE V-16-1-11051 VCS engine join version=188.8.131.52
2012/11/13 21:24:27 VCS NOTICE V-16-1-11052 VCS engine pstamp=6.0.100.000-GA-2012-07-20-16.30.01
2012/11/13 21:24:27 VCS NOTICE V-16-1-10114 Opening GAB library
2012/11/13 21:24:27 VCS INFO V-16-1-10196 Cluster logger started
but, a 'ps -ef | grep had' returns no entry.
The file /var/VRTSvcs/log/hastart.log has this entry for the startup attempt :
File was modified after system boot,
boottime = <1352828351>, modifytime = <1352828394>
[root@localhost log]# view engine_A.log