X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8B133.FA2C3FF0@onstor-exch02.onstor.net>; Thu, 8 May 2008 10:50:17 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Unable to create cluster
Date: Thu, 8 May 2008 10:50:17 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E09DFA036@onstor-exch02.onstor.net>
In-Reply-To: <20080508104005.772fbfb1@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Unable to create cluster
Thread-Index: AcixMpFAuRH5RJkfRjesbDC9421jsgAAVPfg
References: <BB375AF679D4A34E9CA8DFA650E2B04E09DF9FBC@onstor-exch02.onstor.net> <20080508104005.772fbfb1@ripper.onstor.net>
From: "Raj Kumar" <raj.kumar@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Andy,

Both seem to have same time.

[root@c75r2-rh9 tte]# ./execute "system time show"
########## 10.2.208.11 #########
Thu May  8 10:49:26 PDT 2008
########## 10.2.208.12 #########
Thu May  8 10:49:27 PDT 2008
[root@c75r2-rh9 tte]#
[root@c75r2-rh9 tte]#
[root@c75r2-rh9 tte]#

[root@c75r2-rh9 tte]# ./execute "system time show -v"
########## 10.2.208.11 #########
Thu May  8 10:49:30 PDT 2008
assID=3D0 status=3D0644 leap_none, sync_ntp, 4 events, =
event_peer/strat_chg,
version=3D"ntpd 4.2.2p4@1.1585-o Sun Mar  4 14:07:21 UTC 2007 (1)",
processor=3D"mips64", system=3D"Linux/2.6.22-cg", leap=3D00, =
stratum=3D4,
precision=3D-20, rootdelay=3D109.370, rootdispersion=3D157.497, =
peer=3D40397,
refid=3D10.2.0.7,
reftime=3Dcbcdba2d.8699b304  Thu, May  8 2008 10:43:09.525, poll=3D6,
clock=3Dcbcdbbaa.523a2640  Thu, May  8 2008 10:49:30.321, state=3D4,
offset=3D4.646, frequency=3D5.152, jitter=3D11.188, noise=3D5.117,
stability=3D0.024, tai=3D0
     remote           refid      st t when poll reach   delay   offset
jitter
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D=3D=3D
*10.2.0.7        10.0.0.18        3 u   57   64  377    0.468    4.646
5.698
 10.0.0.18       .INIT.          16 -    -   64    0    0.000    0.000
0.000

########## 10.2.208.12 #########
Thu May  8 10:49:30 PDT 2008
assID=3D0 status=3D0644 leap_none, sync_ntp, 4 events, =
event_peer/strat_chg,
version=3D"ntpd 4.2.2p4@1.1585-o Sun Mar  4 14:07:21 UTC 2007 (1)",
processor=3D"mips64", system=3D"Linux/2.6.22-cg", leap=3D00, =
stratum=3D3,
precision=3D-20, rootdelay=3D62.351, rootdispersion=3D101.309, =
peer=3D7840,
refid=3D10.0.0.18,
reftime=3Dcbcdbb9c.8053575d  Thu, May  8 2008 10:49:16.501, poll=3D7,
clock=3Dcbcdbbaa.f0800776  Thu, May  8 2008 10:49:30.939, state=3D4,
offset=3D14.674, frequency=3D3.015, jitter=3D7.388, noise=3D15.410,
stability=3D0.385, tai=3D0
     remote           refid      st t when poll reach   delay   offset
jitter
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D=3D=3D
*10.0.0.18       192.5.41.41      2 u   14  128  377    0.370   14.674
7.388

Thanks.

-----Original Message-----
From: Andy Sharp=20
Sent: Thursday, May 08, 2008 10:40 AM
To: Raj Kumar
Subject: Re: Unable to create cluster

Raj,

Related to a bug in my queue, could you do me a favor and check the
date on both nodes?  If they are not the same, let me know.

Thanks,

a

On Thu, 8 May 2008 10:08:48 -0700 "Raj Kumar" <raj.kumar@onstor.com>
wrote:

> Hi,
>=20
> I am trying to create a 2 node coughar cluster. After I added the
> second node, the clusterDB syncbetween 2 nodes has been going on for
> last 25 minutes but still the cluster is not up. On both the nodes
> there are nothing configured in the clusterDB. Not sure why this is
> taking this much time. How do I get this cluster working now?
>=20
> The second node:
>=20
> May  8 09:51:27 g11r208 : 0:0:cluster2:NOTICE: Ubik: SDISK_SendFile:
> Synchronize database with server 10.2.208.12, version 0x48232f6f:2=20
> May  8 09:51:28 g11r208 : 0:0:cluster2:NOTICE: Ubik: SDISK_SendFile:
> Synchronize database with server 10.2.208.12 completed=20
> May  8 09:51:40 g11r208 : 0:0:eventd:WARNING: Process-EVENT 0.0.0.0:
> Mgmt Port 0.0.0.0 PCC, State Up
> May  8 09:52:03 g11r208 : 0:0:nfxsh:NOTICE: cmd[3]: vsvr show  :
> status[11]
> May  8 09:52:04 g11r208 : 0:0:cluster2:ERROR: cluster_iSendMsgHdr:
> mismatch rc -1, size 968, msgId 10419=20
> May  8 09:52:05 g11r208 : 0:0:cluster2:ERROR: cluster_iSendMsgHdr:
> mismatch rc -1, size 52, msgId 10419=20
> May  8 09:52:30 g11r208 : 0:0:cluster2:ERROR: cluster_iSendMsgHdr:
> mismatch rc -1, size 968, msgId 10419=20
> May  8 09:52:56 g11r208 : 0:0:cluster2:ERROR: cluster_iSendMsgHdr:
> mismatch rc -1, size 968, msgId 10419=20
> May  8 09:53:14 g11r208 : 0:0:cluster2:ERROR: cluster_iSendMsgHdr:
> mismatch rc -1, size 52, msgId 10419=20
> May  8 09:53:22 g11r208 : 0:0:cluster2:ERROR: cluster_iSendMsgHdr:
> mismatch rc -1, size 968, msgId 10419=20
> May  8 09:53:45 g11r208 : 0:0:cluster2:ERROR: cluster_iSendMsgHdr:
> mismatch rc -1, size 0, msgId 10422=20
> May  8 09:53:49 g11r208 : 0:0:cluster2:ERROR: cluster_iSendMsgHdr:
> mismatch rc -1, size 968, msgId 10419=20
> May  8 09:53:55 g11r208 : 0:0:nfxsh:NOTICE: cmd[4]: cluster show
> cluster : status[0]
> May  8 09:54:00 g11r208 : 0:0:nfxsh:NOTICE: cmd[5]: syst sh ver :
> status[0]
> May  8 09:54:15 g11r208 : 0:0:cluster2:ERROR: cluster_iSendMsgHdr:
> mismatch rc -1, size 968, msgId 10419=20
> May  8 09:54:24 g11r208 : 0:0:cluster2:ERROR: cluster_iSendMsgHdr:
> mismatch rc -1, size 52, msgId 10419=20
> May  8 09:54:41 g11r208 : 0:0:cluster2:ERROR: cluster_iSendMsgHdr:
> mismatch rc -1, size 968, msgId 10419=20
> May  8 09:55:07 g11r208 : 0:0:cluster2:ERROR: cluster_iSendMsgHdr:
> mismatch rc -1, size 968, msgId 10419=20
> May  8 09:55:14 g11r208 : 0:0:cluster2:ERROR: cluster_iSendMsgHdr:
> mismatch rc -1, size 0, msgId 10422
>=20
> The first node that issued cluster commit:
>=20
> May  8 10:06:35 g12r208 : 0:0:cluster2:NOTICE: ubeacon_Interact:
> minority pcc elected 10.2.208.12=20
> May  8 10:06:35 g12r208 : 0:0:cluster2:ERROR: ClusterServ_UpdateState:
> database is synchronizing, not ready=20
> May  8 10:06:38 g12r208 : 0:0:cluster2:NOTICE: ubeacon_Interact:
> minority pcc elected 10.2.208.12=20
> May  8 10:06:38 g12r208 : 0:0:cluster2:ERROR: ClusterServ_UpdateState:
> database is synchronizing, not ready=20
> May  8 10:06:41 g12r208 : 0:0:cluster2:NOTICE: ubeacon_Interact:
> minority pcc elected 10.2.208.12=20
> May  8 10:06:41 g12r208 : 0:0:cluster2:ERROR: ClusterServ_UpdateState:
> database is synchronizing, not ready=20
> May  8 10:06:44 g12r208 : 0:0:cluster2:NOTICE: ubeacon_Interact:
> minority pcc elected 10.2.208.12=20
> May  8 10:06:45 g12r208 : 0:0:cluster2:ERROR: ClusterServ_UpdateState:
> database is synchronizing, not ready=20
> May  8 10:06:47 g12r208 : 0:0:cluster2:NOTICE: ubeacon_Interact:
> minority pcc elected 10.2.208.12=20
> May  8 10:06:48 g12r208 : 0:0:cluster2:ERROR: ClusterServ_UpdateState:
> database is synchronizing, not ready=20
> May  8 10:06:50 g12r208 : 0:0:cluster2:NOTICE: ubeacon_Interact:
> minority pcc elected 10.2.208.12=20
> May  8 10:06:51 g12r208 : 0:0:cluster2:ERROR: ClusterServ_UpdateState:
> database is synchronizing, not ready
