From: Matt Garman <garman@raw-sewage.net>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] extreme clock drift / openntpd won't sync
Date: Wed, 31 Aug 2005 17:13:33 -0500 [thread overview]
Message-ID: <20050831221333.GA8710@raw-sewage.net> (raw)
My system clock is running extremely fast... so fast that even
openntpd (apparently) can't catch up!
I tried (oh how I tried) to get the "regular" ntp package to work.
I could correct my clock using ntpdate, but I could never get ntpd
to sync with any servers (see notes (*) below).
So I got fed up with trying to get it to work, and thought I'd have
better luck with openntpd (which is much simpler).
As far as I can tell, openntpd *is* working, as I have many lines in my
syslog that look like this:
Aug 31 17:00:36 [ntpd] adjusting local clock by -344.003180s
However, the clock is still drifting---not as fast as it does with no
ntp daemon running, but noticeably (it's gained about 5 minutes in less
than 24 hours). Note that without any ntp daemon running, my clock will
gain about 10 minutes per hour!
I have a hunch that whatever prevented the "regular" ntpd from syncing
is preventing openntpd from properly keeping the clock in sync.
So, my questions are: (1) what would cause my clock to run so fast? And
(2) why can't any ntp daemon keep correct time?
Thanks,
Matt
(*) If anyone is interested in the plight I had with ntp, here is some
info:
This is what my /etc/ntp.conf looked like:
restrict 127.0.0.1 nomodify
server pool.ntp.org prefer
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
server 127.127.1.1
fudge 127.127.1.1 stratum 10
driftfile /var/lib/ntp/ntp.drift
logfile /var/log/ntpd.log
After starting ntpd, and waiting a while, ntpq results looked like
this:
ntpq> pe
remote refid st t when poll reach delay offset jitter
==============================================================================
frigg.interstro 138.195.130.71 3 u 21 128 377 124.592 -3950.7 1260.34
cteha.ulp.co.il 192.114.62.249 3 u 26 128 377 201.236 -4670.9 1715.95
Time4.Stupi.SE .PPS. 1 u 79 128 377 129.134 -1668.9 1996.01
Time1.Stupi.SE 193.10.7.246 2 u 21 128 377 128.697 -3962.7 1253.70
*LOCAL(1) LOCAL(1) 10 l 13 64 377 0.000 0.000 0.001
ntpq> assoc
ind assID status conf reach auth condition last_event cnt
===========================================================
1 57708 9014 yes yes none reject reachable 1
2 57709 9014 yes yes none reject reachable 1
3 57710 9014 yes yes none reject reachable 1
4 57711 9014 yes yes none reject reachable 1
5 57712 9614 yes yes none sys.peer reachable 1
--
Matt Garman
email at: http://raw-sewage.net/index.php?file=email
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2005-08-31 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 22:13 Matt Garman [this message]
2005-08-31 22:56 ` [gentoo-user] extreme clock drift / openntpd won't sync William Kenworthy
2005-09-01 0:36 ` Matt Randolph
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050831221333.GA8710@raw-sewage.net \
--to=garman@raw-sewage.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox