Export (0) Print
Expand All

Joining a Cluster (Unsuccessful Attempt)

The entries in this section are the record of a failed JOIN operation. They record the attempts of the joining node to find a sponsor from the available addresses and node names.

The first entry is a state entry, reporting the [INIT] state of the node attempting to join.

378.380::1999/06/09-18:00:19.734 [INIT] Attempting to join cluster

CLUSTER1

In all the following entries, the state of the node is [JOIN].

The following nine entries record the spawning of threads that try to connect to the sponsor node and record the node's requests to join the cluster. The service always tries to join a cluster through the following:

  • Cluster's IP address (172.16.64.254).

  • Sponsor's name (NODE2).

  • Network interfaces that are marked for internal cluster communication on the sponsor node. In this example, that includes the sponsor node's IP addresses 172.16.64.2 and 10.10.0.2.

378.380::1999/06/09-18:00:19.742 [JOIN] Spawning thread to connect to

sponsor 172.16.64.254

378.3c4::1999/06/09-18:00:19.742 [JOIN] Asking 172.16.64.254 to sponsor

us.

378.380::1999/06/09-18:00:19.742 [JOIN] Spawning thread to connect to

sponsor 172.16.64.2

378.3c8::1999/06/09-18:00:19.742 [JOIN] Asking 172.16.64.2 to sponsor

us.

378.380::1999/06/09-18:00:19.742 [JOIN] Spawning thread to connect to

sponsor 10.10.0.2

378.3cc::1999/06/09-18:00:19.742 [JOIN] Asking 10.10.0.2 to sponsor us.

378.380::1999/06/09-18:00:19.742 [JOIN] Spawning thread to connect to

sponsor NODE2

378.380::1999/06/09-18:00:19.742 [JOIN] Waiting for all connect threads

to terminate.

378.3d0::1999/06/09-18:00:19.742 [JOIN] Asking NODE2 to sponsor us.

The following entries report the failures (or successes) of the requests to join. Using the net helpmsg error number command, you can find out that "status=1722" means "The RPC server is unavailable." In other words, the node attempting to join cannot contact the Cluster service on the target node.

Note the consistency of the process ID in both the request entry and response entries. Note also the consistency of the thread ID for each thread generated to a given sponsor.

378.3c8::1999/06/09-18:00:46.600 [JOIN] Sponsor 172.16.64.2 is not

available (JoinVersion), status=1722.

378.3c4::1999/06/09-18:00:46.600 [JOIN] Sponsor 172.16.64.254 is not

available (JoinVersion), status=1722.

378.3cc::1999/06/09-18:00:46.600 [JOIN] Sponsor 10.10.0.2 is not

available (JoinVersion), status=1722.

378.3c8::1999/06/09-18:00:46.600 [JOIN] JoinVersion data for sponsor

172.16.64.2 is invalid, status 1722.

378.3c4::1999/06/09-18:00:46.600 [JOIN] JoinVersion data for sponsor

172.16.64.254 is invalid, status 1722.

378.3cc::1999/06/09-18:00:46.600 [JOIN] JoinVersion data for sponsor

10.10.0.2 is invalid, status 1722.

378.3d0::1999/06/09-18:00:46.615 [JOIN] Sponsor NODE2 is not available

(JoinVersion), status=1722.

378.3d0::1999/06/09-18:00:46.615 [JOIN] JoinVersion data for sponsor

NODE2 is invalid, status 1722.

All the threads are terminated; failure to find a sponsor for joining a cluster is reported; and, consequently, failure of the attempted join is reported:

378.380::1999/06/09-18:00:46.615 [JOIN] All connect threads have

terminated.

378.380::1999/06/09-18:00:46.615 [JOIN] Unable to connect to any sponsor

node.

378.380::1999/06/09-18:00:46.615 [INIT] Failed to join cluster, status

53

Next, the Cluster service on this node tries to form a cluster.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft