Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-06 Thread PGNet Dev
On Tue, Oct 6, 2009 at 8:19 PM, Patrick Domack wrote: > If you want to email a list that normally no traffic, but many people > willing to help with ntp, try timekeep...@fortytwo.ch (not sure if you have > to subscribe to send emails) good reference, and good advice --> http://fortytwo.ch/mailman

Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-06 Thread Patrick Domack
Hmm, I forgot to respond to this :) I believe it's working for you, cause you last set dom0 to use it's own clock, instead of xen, so now dom0's clock is getting synced via ntp. BUT the ALL of your domU's now, have no time sync. If your clock in your computer is good, then all is fine (ex

Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-06 Thread Patrick Domack
If you notice in your ntpq dumps you did, you have >400ms of jitter. That is a hell of alot. I dunno if it makes a difference but you used 3 servers from the same edu, and they have 90ms on them, shouldn't matter, if they where the only ones with jitter I would replace them, but all 4 of your

Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-06 Thread PGNet Dev
just fwiw, as of 10/06/09 19:03:27 still no errors. apparently, time's moving forward again ... so, it seems the config above works. why some others have NOT seen the same problems, remains for me a bit of a mystery.

Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-06 Thread PGNet Dev
> The wiki page also suggests clockspeed or chrony if ntpd can't seem to > keep the time correct. Maybe one of those helps. Hmm. The Chrony's web > site seems to be gone, wonder if it has a new one somewhere.. sure, but with the _widespread_ use of ntp(d), this bears investigation. and, unfortuna

Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-06 Thread Timo Sirainen
On Tue, 2009-10-06 at 11:24 -0700, PGNet Dev wrote: > and, of course, immediately after hitting 'Send', i see in logs, > > Oct 06 11:22:08 dovecot: Error: Time just moved backwards by 1 > seconds. I'll sleep now until we're back in present. > http://wiki.dovecot.org/TimeMovedBackwards > > Oct 6

Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-06 Thread PGNet Dev
and, of course, immediately after hitting 'Send', i see in logs, Oct 06 11:22:08 dovecot: Error: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards Oct 6 11:22:07 mx ntpd[17697]: time reset -2.075483 s Oct 6 11:22:16 mx

Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-06 Thread PGNet Dev
progress, i think. thanks to all for comments. referencing, http://www.novell.com/communities/node/8629/time-synchronization-xen-setup http://www.linux.org.za/Lists-Archives/glug-tech-0905/msg00271.html http://www.gossamer-threads.com/lists/linux/kernel/1039416 i've decoupled DomU's time s

Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-06 Thread Patrick Domack
This reminds me of an odd issue I had also, where mine stepped at a given amount per time too. In the datacenter one server was at limited it to 10mbit half duplex, and I had endless ntp issues. I could only replicate this offsite with the same server using 10mbit and fully saturating the n

Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-06 Thread Rob Middleton
On 6/10/2009 12:54 PM, PGNet Dev wrote: looking at my ntp logs around the same time(s). ... 5 Oct 16:41:17 ntpd[5696]: synchronized to 64.125.78.85, stratum 1 5 Oct 16:51:38 ntpd[5696]: time reset -2.140133 s 5 Oct 16:56:40 ntpd[5696]: synchronized to 66.220.9.122, stratum 1 5 Oct 17:

Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-06 Thread Patrick Domack
Hmm, I have been running dovecot inside xen for almost 3 years now without any time issues. I checked my logs and I have no ntp time reset messages for the last month. I think it's more possible ntp is stepping the time instead of slewing it (http://www.ntp.org/ntpfaq/NTP-s-algo.htm section

Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-06 Thread Thierry DOSTES
Hi, Here comes an extract from Debian Wiki about Xen to allow a domU to keep its own time : (...) your domU is likely using the xen clocksource instead of its own clock ticks. In practice, this seems to be the cause of infrequent lockups under load (and/or problems with suspending). A w

Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-05 Thread PGNet Dev
hi, On Mon, Oct 5, 2009 at 4:02 PM, Timo Sirainen wrote: > And no ntpd in your DomU? nope. service ntp status Checking for network time protocol daemon (NTPD): unused >> any suggestions as to what/how to fix? > > If no one here can give you a good answer, I'd try some Xen mailing > list.

Re: [Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-05 Thread Timo Sirainen
On Mon, 2009-10-05 at 18:54 -0700, PGNet Dev wrote: > i'm running Dovecot in a Xen DomU, .. > @ my Dom0, > > ps ax | grep ntp\.conf >5696 ?Ss 1:05 /usr/sbin/ntpd -p > /var/run/ntp/ntpd.pid > -g -u ntp:ntp -i /var/lib/ntp -c /etc/ntp.conf And no ntpd in your DomU

[Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

2009-10-05 Thread PGNet Dev
i've dovecot --version 1.2.5 hg log | grep changeset | head -n 1 changeset: 9407:a3e16df805e3 in my logs, i'm seeing ... Oct 05 16:51:40 dovecot: Error: Time just moved backwards by 1 seconds. I'll sleep now until we're back in pr