Forum Discussion

br1's avatar
br1
Level 3
11 years ago

VCS Cluster not starting.

Hello All, I am having difficulties trying to get VCS started on this system. I have attached what I have got so far. I apperciate any comments or suggestions as to go from here. Thank you ...
business continuity
Cluster Server
Solaris
Troubleshooting
  • AHerr's avatar
    AHerr
    11 years ago

    If only one of two nodes can connect through llt (see your lltstat -nvv where one node is present and the other is down) then the cluster will attempt to start but will wait for both nodes to be available.

    This is done to ensure in a heartbeat disconnection scenario or split-brain condition that you do not have 2 seperate clusters starting.

    If this is a known condition, you can run the command

    # gabconfig -C -X

    This removes the number of nodes needed to seed a cluster, but this command should only be performed if you are certain the other node does not already have a running cluster.  You should also diagnose why the other nodes' heartbeat links are not visable from llt.

     

g_lee's avatar
g_lee
Level 6
11 years ago

From the error you posted:

hastart   / hastart -onenode
dmesg: Exiting: Another copy of VCS may be running

... unless you killed the previous version of had/hastart (that would have started automatically on boot and was probably still running waiting for gab membership from the other node(s)), it looks like hastart -onenode failed as it found the other copy of had already running.

Note the following from the man page:

-onenode

Use this option only to start VCS on a single system where LLT and GAB are not required. Do not use this option to start VCS on a node in a multisystem cluster.

So you shouldn't be using this option to start had in a cluster with more than one node - use the gabconfig -c -x procedure provided by AHerr if there are known LLT/network issues (note you need to ensure the second/other node is definitely down or you may end up with some issues eg: a split brain cluster)