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
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
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
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.
> 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
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
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
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
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
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:
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
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
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.
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
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
On some FreeBSD 6.2 systems I was solved this problem just by adding to crontab:
@hourly/sbin/sysctl `/sbin/sysctl -e machdep.adjkerntz` >/dev/null 2>&1
For some explanation, see:
http://lists.freebsd.org/pipermail/freebsd-hackers/2005-August/013383.html
Quote follows:
... It seems that
On Sat, Jan 19, 2008 at 11:07:58AM -0500, Charles Marcus wrote:
On 1/19/2008 Luigi Rosa wrote:
>> On one hand we have Dovecot that kill itself until someone kicks it back
>> on, on the other hand we have just some errors on the logfile.
>>
>> Well, IMHO at least there could be a configuration
On 1/19/2008 Luigi Rosa wrote:
On one hand we have Dovecot that kill itself until someone kicks it
back on, on the other hand we have just some errors on the logfile.
Well, IMHO at least there could be a configuration parameter that
allows me to choose between a service that kills itself and s
Gunter Ohrner said the following on 19/01/08 16:51:
That's why I suggested to use ntpdate to force the correct time to be set
before ntpd even starts and the ntp init script returns.
Admittedly, this won't work if you have no network connectivity during
boot up, but if you have, this paticular
Hi!
Am Samstag, 19. Januar 2008 schrieb Luigi Rosa:
> > How about first starting ntpd, forcing a time-update using ntpdate
> > even before starting ntpd, and delaying the dovecot start until after
> > the time has been adjusted?
> The problem is tha you cannot tell when the time is adjusted becaus
Karsten Bräckelmann said the following on 19/01/2008 13.26:
But the system clock was 45 minutes ahead, so:
No. :)
You'r right, my mistake.
Exactly one hour. Doesn't strike me as a coincidence...
Don't know. That machine had a very long uptime. The system is
configured to have the hardware
Gunter Ohrner said the following on 19/01/08 16:47:
Mh, sounds as if the system clock is set to "local time", including DST
changes, and the system clock had not yet been adjusted... I know why I
use UTC for the system clock on my machines... ;)
Probably. As I said the server lost power witho
Am Samstag, 19. Januar 2008 schrieb Karsten Bräckelmann:
> > 2 Jan 19 10:31:55 gw ntpd[2112]: time reset -3600.221385 s
> Exactly one hour. Doesn't strike me as a coincidence...
Mh, sounds as if the system clock is set to "local time", including DST
changes, and the system clock had not yet been
Ralf Hildebrandt said the following on 19/01/2008 13.16:
Solution: Start ntpdate/ntpd FIRST.
It's what I did, but it could not solve this specific issue.
Unfortunately, server and ADSL modem router went back online together
and the ADSL router takes more time to go online than the server
(b
nc enabled 0001
> Jan 19 10:31:55 gw dovecot: Time just moved backwards by 3600 seconds.
> This might cause a lot of problems, so I'll just kill myself now.
> http://wiki.dovecot.org/TimeMovedBackwards
Exactly one hour. Doesn't strike me as a coincidence...
guenther
--
char *
chronized to 62.48.35.100, stratum 2
> Jan 19 10:31:55 gw ntpd[2112]: time reset -3600.221385 s
> Jan 19 10:31:55 gw ntpd[2112]: kernel time sync enabled 0001
> Jan 19 10:31:55 gw dovecot: Time just moved backwards by 3600 seconds. This
> might cause a lot of problems, so I
-3600.221385 s
Jan 19 10:31:55 gw ntpd[2112]: kernel time sync enabled 0001
Jan 19 10:31:55 gw dovecot: Time just moved backwards by 3600 seconds.
This might cause a lot of problems, so I'll just kill myself now.
http://wiki.dovecot.org/TimeMovedBackwards
Ciao,
luigi
--
/
+--[Luigi Rosa]--
\
Spoo
On Mon, 2007-12-31 at 09:19 -0500, Neal Becker wrote:
> This wins the 2007 award for strangest (or most amusing) log message:
>
> dovecot: Time just moved backwards by 13 seconds. This might cause a lot of
> problems, so I'll just kill myself now.
>
> It does, unfortunat
On 12/31/2007, Neal Becker ([EMAIL PROTECTED]) wrote:
This wins the 2007 award for strangest (or most amusing) log message:
dovecot: Time just moved backwards by 13 seconds. This might cause a
lot of problems, so I'll just kill myself now.
It does, unfortunately, leave dovecot dead,
This wins the 2007 award for strangest (or most amusing) log message:
dovecot: Time just moved backwards by 13 seconds. This might cause a lot of
problems, so I'll just kill myself now.
It does, unfortunately, leave dovecot dead, which was pretty mysterious to
me. Maybe it could re-exec instead?
2007/4/17, Michal Soltys <[EMAIL PROTECTED]>:
Chaos Engine wrote:
>
> Of course my onboard clock is constantly off by more than 5 secs.
> I don't want
> to abandon time synchronization and I want to use dovecot. Maybe a
> -HUP signal would do? What do you propose?
>
>
Not too long ago there was
Chaos Engine wrote:
Of course my onboard clock is constantly off by more than 5 secs.
I don't want
to abandon time synchronization and I want to use dovecot. Maybe a
-HUP signal would do? What do you propose?
Not too long ago there was a similar question. You can simply recompile
dovecot wi
On 09/04/2007 03:24, Sean Kamath wrote:
On Apr 8, 2007, at 2:20 PM, Bill Cole wrote:
It is important for people to understand how much simpler it is now to
run basically functional and non-abusive NTP than it was even 5 years
ago. The work put into making pool.ntp.org usable has essentially
e
On Apr 8, 2007, at 2:20 PM, Bill Cole wrote:
You should *NEVER* have the clock jump back in time (except during
DST changes -- yuk).
DST changes (at least on sane systems) do not change the system
clock time. Time zones are a cosmetic feature, i.e. how humans are
shown a description of ti
At 12:03 PM -0700 4/8/07, Sean Kamath wrote:
[...]
It's not just dovecot, by the way. MANY things don't like have time
move backward, like Cron, at, etc.
Absolutely.
You should *NEVER* have the clock jump back in time (except during
DST changes -- yuk).
DST changes (at least on sane sys
dovecot suicides with:
"dovecot: Time just moved backwards by 11 seconds. This might
cause a lot of
problems, so I'll just kill myself now."
Of course my onboard clock is constantly off by more than 5 secs.
How "of course?"
The last time I had a machine's NTP synch st
Chaos Engine wrote:
Hi there,
I got a daily cron (rdate to local time server) job wich adjusts time and
which constantly gives me headache.
Every day my dovecot suicides with:
"dovecot: Time just moved backwards by 11 seconds. This might cause a
lot of
problems, so I'll just kill
At 7:25 PM +0200 4/8/07, Chaos Engine wrote:
Hi there,
I got a daily cron (rdate to local time server) job wich adjusts time and
which constantly gives me headache.
Every day my dovecot suicides with:
"dovecot: Time just moved backwards by 11 seconds. This might cause a lot of
problems, so
r) job wich adjusts time and
which constantly gives me headache.
Every day my dovecot suicides with:
"dovecot: Time just moved backwards by 11 seconds. This might cause a lot of
problems, so I'll just kill myself now."
Of course my onboard clock is constantly off by more than 5
Hi there,
I got a daily cron (rdate to local time server) job wich adjusts time and
which constantly gives me headache.
Every day my dovecot suicides with:
"dovecot: Time just moved backwards by 11 seconds. This might cause a lot of
problems, so I'll just kill myself now."
Of co
40 matches
Mail list logo
