May 27, 2003 at 2:36 pm
We received a message in our event log that states, "Cluster node "Svr1" was removed from the active cluster membership. The Clustering Service may have been stopped on the node, the node may have failed, or the node may have lost communication with the other active cluster nodes".
We now have a cluster with only 1 active node!
This all started happening about the time that security updated the password to the account that is used by all our services.
1) How can we verify everthing is in sync with the new password?
2) How do we add the node back in that is now removed from the cluster?
Thanks
Darren
Darren
May 27, 2003 at 2:40 pm
I would check all the sql and cluster services and make sure the password is good. Did the node get evicted from the cluster group or does it show as offline? If it is just off line it may be possible to just correct the logins and restart the server. If it has been evicted, I don't know you may be able to re-add it from the cluster administrator like you would any other win2k box I don't know what it would do to sql at all.
Wes
May 27, 2003 at 3:02 pm
I'll check the passords, thanks.
It hasn't been evicted. It just lost communication. However, I can ping the server and it sees it. Also, should the Cluster Service always be running on both nodes? I just noticed it's stopped on inactive node.
Darren
Darren
May 27, 2003 at 6:03 pm
Cluster Service must be running at all times on all nodes.
May 28, 2003 at 7:16 am
I think we found the root cause. The MSDTC had stopped and was unable to start. The error said that it can't start because it wasn't configured to run in a cluster. Please run comclust.exe. This doesn't make sense because it was previously running in a cluster. Can I run this safely and not affect anything? And then try to start the service?
Darren
Darren
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply