Forum Discussion

Rao_Yunjia's avatar
Rao_Yunjia
Level 3
9 years ago

VCS engine (had) cann't start automatically

 this is the only node of the cluster1 that I am trying to start VCS.

as my experience, after SFHA installation, the veritas can start automatically with Solaris OS boot.

the below is the procedure of my operation

1.after SFHA installation, I found it cann't run "vxdisk list" command, it showing "Configuration daemon is not accessible"

so I follow the article and solved it https://www.veritas.com/support/en_US/article.TECH67777

2.then, i completed the synchronization between cluster1 and cluster2

3.when I try to config GCO with gcoconfig, it cann't work as well.at that time,I reboot the Solaris OS once and found it persist after reboot. so I try to start veritas with command "hastart -onenode" then I can config the GCO.

4.I completed all veritas configuration cluster1 and cluster 2 both.

5.I reboot the node of cluster1 and cluster2, after reboot, I found only the host of cluster1 cannot accese by VCS_Cluster_Manager_Java_Console. it show VCS ERROR V-16-10-106. But the host of cluster2 is fine.

please advice me.thanks in advance.

the detail information has been attached in files.

 

 

  • after running "hastart -onenode', I can access node of cluster1 by VCS_Cluster_Manager_Java_Console

    But I need vcs engine start automatically rather than running it manuallly.

  • You did not mention your VCS version or exact steps you performed to configure SF or VCS.

    Have you seen this topic in VCS Installation Guide?

    Configuring VCS in single node mode

    In addition to the steps mentioned in the manual configuration section, complete the following steps to configure VCS in single node mode.
    (See manual for details...)

     

    *** EDIT ***

    Duplicate post.

    See https://www.veritas.com/community/forums/vcs-engine-had-cannt-start-automatically