AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070110120536.327050ea@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<chris.vandever@onstor.com>,<john.keiffer@onstor.com>,<dl-software@onstor.com>,<dl-qa@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E0138C3EA@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 10 Jan 2007 12:05:51 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Chris Vandever" <chris.vandever@onstor.com>
Cc: "John Keiffer" <john.keiffer@onstor.com>, "dl-Software"
 <dl-software@onstor.com>, "dl-QA" <dl-qa@onstor.com>
Subject: Re: time difference issue
Message-ID: <20070110120551.177b5e47@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0138C3EA@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E01FF8CBC@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0138C3EA@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

The ntp daemon itself also has a threshold for the time difference,
beyond which it will give up and not try to close the gap, as it deems
it to be too great.  For cases where the time delta is too great, the
ntpdate program should be used to jump the date forward (or backward).
After taking into consideration the things Chris mentions below, of
course.

Cheers,

a

 On Wed, 10 Jan 2007 11:39:11 -0800 "Chris Vandever"
<chris.vandever@onstor.com> wrote:

> I believe it takes awhile for NTP to adjust the time to what it gets
> from the NTP server.  If we were to simply change it immediately a lot
> of things might break (premature timeouts, etc.), especially if we're
> 'fast'.
> 
>  
> 
> Forwarding to dl-QA, as they have more experience than I do on how
> long you should expect it to take for NTP to synchronize time across
> multiple nodes.
> 
>  
> 
> ChrisV
> 
>  
> 
> ________________________________
> 
> From: John Keiffer 
> Sent: Wednesday, January 10, 2007 11:30 AM
> To: dl-Software
> Subject: FW: time difference issue
> 
>  
> 
> Hello all,
> 
>  
> 
> Please see my original email below. Can someone explain further?
> 
>  
> 
> Thanks,
> 
> John
> 
>  
> 
> ________________________________
> 
> From: Nagendra Subramanya 
> Sent: Wednesday, January 10, 2007 11:19 AM
> To: John Keiffer
> Subject: RE: time difference issue
> 
>  
> 
> John,
> 
> I don't know about other daemons that are affected by addition/removal
> of NTP servers.
> 
> I think clusterDB related daemons may be affected.
> 
> Please post your question to dl-Software so that others may comment on
> your scenario.
> 
>  
> 
> -Nags
> 
>  
> 
> ________________________________
> 
> From: John Keiffer 
> Sent: Wednesday, January 10, 2007 9:05 AM
> To: Nagendra Subramanya
> Subject: time difference issue
> 
>  
> 
> Hey Nagendra,
> 
>  
> 
> I know you said the following message is just informational, but I'm
> trying to understand in which places the time is computed to be
> different. I added NTP servers to both my nodes, but found that the
> ssc_console times where still not correct. Is this where the time
> difference is happening? After I rebooted BOTH nodes, then everything
> was in sync and NCM was accessible again.
> 
>  
> 
> "auth_agent:INFO: authAgent_checkForReqTimeouts: 5825: Timedifference
> is computed to be greater than 1 sec: 2"
> 
>  
> 
> Thank you,
> 
> John Keiffer
> 
>  
> 
>  
> 
