Node Cannot Form Cluster Because Quorum Location Changed

  • Article

In the following log, the quorum location was changed while the Cluster service was turned off on node 1. After the quorum location was changed and before the Cluster service was restarted on node 1, the Cluster service was turned off on the other node. In this log, the initialization of the Cluster service and the formation of the cluster proceeds normally until the events described by the entries in this section. For the cluster log output of a normal cluster formation operation, see "Forming a Cluster," earlier in this chapter.

The portion of the cluster log reproduced here starts after the Cluster service has done the following:

  • Was unable to find a node to sponsor this node's attempt to join the cluster.

  • Started a form operation.

  • Created the Cluster group and the resources in the Cluster group and then brought them online.

  • Started arbitration for and obtained ownership of the Quorum resource and then brought it online.

The Cluster service now tries to open the quorum log:

00000460.00000598::1999/10/21-23:58:30.621 [INIT] Attempting to form

cluster CLUSTER10

00000460.00000598::1999/10/21-23:58:30.746 [FMX] Found the quorum

resource a83b4084-3391-4618-890e-8794d4df923b.

.

.

.

The following entry demonstrates that, according to the node's copy of the cluster configuration database, the quorum location is E:\MSCS\Quolog.log. However, while the node was offline, the quorum directory was moved to another location. Because the other node in the cluster went offline before the Cluster service was restarted on this node, this node cannot get the actual current quorum location.

00000460.0000042c::1999/10/21-23:58:31.152 [DM] DmpQuoObjNotifyCb: the

name of the quorum file is E:\MSCS\quolog.log

.

.

.

Note in the following entries that until the Database Manager reports checking for a quorum tombstone and finding one, the node seems able to form a cluster.

00000460.0000042c::1999/10/21-23:58:31.168 [LM] LogpCreate : Exit with

success

00000460.0000042c::1999/10/21-23:58:31.184 [DM] DmpQuoObjNotifyCb:

Quorum log opened

00000460.0000042c::1999/10/21-23:58:31.184 [FM]

HandleResourceTransition: Resource Name =

a83b4084-3391-4618-890e-8794d4df923b old state=129 new state=2

00000460.0000042c::1999/10/21-23:58:31.184 [FM]

FmpPropagateResourceState: signalling the ghQuoOnlineEvent

00000460.00000598::1999/10/21-23:58:31.184 [DM] DmpChkQuoTombStone

Entry

.

.

.

In the following two entries, the Database Manager reports that a tombstone file for an old location of the quorum directory was found. For more information about tombstones, see "Applying Quorum Log Changes to the Cluster Database" earlier in this chapter.

00000460.00000598::1999/10/21-23:58:31.199 [DM] DmpChkQuoTombStone:A

tombstone for this resource, and quorum log file was found here.

00000460.00000598::1999/10/21-23:58:31.199 [DM] DmpChkQuoTombStone:This

is node is only allowed to do a join, make sure another node forms

.

.

.

Finally, the following entry indicates that the Cluster service is shutting down.

000001bc.000004dc::1999/10/21-23:58:32.902 [RM] NotifyChanges shutting

down.