X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8B9FF.127A5790@onstor-exch02.onstor.net>; Mon, 19 May 2008 15:24:15 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: Is this an NTP problem?
Date: Mon, 19 May 2008 15:24:15 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0A0F845C@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Is this an NTP problem?
Thread-Index: Aci5/xI3GTwMB2ylTayyWxDLuQyBEA==
From: "Rich LaReau" <rich.lareau@onstor.com>
To: "dl-cstech" <dl-cstech@onstor.com>


I'm getting these chunks of logs every so often.  Is the whole set
related to NTP being off by seven seconds?   If so, I should post them
to our NTP troubleshooting Wiki.

And also, what was the consensus on "kicking" the times so that they
match again?  Restart ntpd, or delete/add the ntp servers?

Thanks,
Rich


May 19 15:36:34 fss-pnasgw2 : 0:0:cluster2:INFO:
ClusterCtrl_iUpdateState: post pcc up pccname fss-pnasgw2=20
May 19 15:36:34 fss-pnasgw2 : 0:0:cluster2:WARNING: remote host
10.210.17.72 (time tic =3D 1211232980) and local (time tic =3D
1211232994)times are not synchronized. Please verify NTP server setup.=20
May 19 15:36:34 fss-pnasgw2 : 0:0:auth_agent:WARNING:
cleanCurrentRequest: cifsd exited while processing request with type
10321 1 time, retrying=20
May 19 15:36:34 fss-pnasgw2 : 0:0:auth_agent:WARNING: cifsd for vs 3
exited. Restarting it=20
May 19 15:36:34 fss-pnasgw2 : 0:0:auth_agent:INFO:
authen_restartCifsDaemon: Restarting CIFS daemon=20
May 19 15:36:34 fss-pnasgw2 : 0:0:eventd:WARNING: Process-EVENT 0.0.0.0:
Mgmt Port 0.0.0.0 PCC, State Up
May 19 15:36:36 fss-pnasgw2 : 0:0:cluster2:NOTICE: urecovery_Interact:
send new file in progress, remote ver 0(0), sending to 10.210.17.72=20
May 19 15:36:36 fss-pnasgw2 : 0:0:cluster2:NOTICE: urecovery_Interact:
Rx-write bulk error=3D1=20
May 19 15:36:36 fss-pnasgw2 : 0:0:cluster2:NOTICE: urecovery_Interact:
rx_EndCall error =3D 5381=20
May 19 15:36:36 fss-pnasgw2 : 0:0:cluster2:NOTICE: urecovery_Interact:
send new file end, code 1=20
May 19 15:36:37 fss-pnasgw2 : 0:0:cluster2:WARNING:
ClusterCtrl_iUpdateState: post pcc down pccname fss-pnasgw2=20
May 19 15:36:37 fss-pnasgw2 : 0:0:eventd:CRITICAL: Process-EVENT Node:
Name 'fss-pnasgw2', State Down, Msg ''
May 19 15:36:37 fss-pnasgw2 : 0:0:vtm:INFO: vtm_get_filer_config: fail
to get cluster info, try again later=20
May 19 15:36:46 fss-pnasgw2 last message repeated 2 times
May 19 15:36:47 fss-pnasgw2 : 0:0:sscccc:NOTICE: New client 0: addr
143.199.12.120, port 33693; Assigning fd(12)
May 19 15:36:47 fss-pnasgw2 : 0:0:sscccc:INFO: bad read, bytes=3D-1
(client 0 socket 12)
May 19 15:36:47 fss-pnasgw2 : 0:0:sscccc:NOTICE: closing session for
client 0
May 19 15:36:49 fss-pnasgw2 : 0:0:cluster2:INFO:
ClusterCtrl_iUpdateState: post pcc up pccname fss-pnasgw1=20
May 19 15:36:49 fss-pnasgw2 : 0:0:eventd:WARNING: Process-EVENT 0.0.0.0:
Mgmt Port 0.0.0.0 PCC, State Up
