From: "Aleksey V. Kunitskiy" <alexey.kv@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] ntpd clock adjusting
Date: Fri, 27 Jul 2007 23:45:54 +0300 [thread overview]
Message-ID: <200707272345.57903.alexey.kv@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3894 bytes --]
Hi,
I've just deployed my home server, of course using Gentoo :)
I setup openntpd there and /var/log/messages says to me that every few minutes
clock is adjusted by ~100s. Is it a bug or I've missed smth?
chipset: nForce2
And, btw, what is also strange - ntpd use different time in different log
message types. Actual local time was 22h (GMT+3). System clock is UTC
(note: I've terminated several times ntpd - I've changed servers, I hoped it
help, but...)
thanks for any suggestion
/var/log/messages:
Jul 27 22:07:27 enigma ntpd[32345]: listening on 192.168.3.1
Jul 27 19:07:27 enigma ntpd[32345]: ntp engine ready
Jul 27 19:07:50 enigma ntpd[32345]: peer 129.6.15.29 now valid
Jul 27 19:07:53 enigma ntpd[32345]: peer 129.6.15.28 now valid
Jul 27 22:08:43 enigma ntpd[32344]: adjusting local clock by 102.470196s
Jul 27 19:09:31 enigma ntpd[32345]: peer 129.6.15.29 now invalid
Jul 27 19:10:21 enigma ntpd[32345]: ntp engine exiting
Jul 27 22:10:21 enigma ntpd[32344]: Terminating
Jul 27 22:10:21 enigma ntpd[32677]: listening on 192.168.3.1
Jul 27 19:10:21 enigma ntpd[32677]: ntp engine ready
Jul 27 19:10:45 enigma ntpd[32677]: peer 129.6.15.28 now valid
Jul 27 19:10:45 enigma ntpd[32677]: peer 129.6.15.29 now valid
Jul 27 22:11:46 enigma ntpd[32676]: adjusting local clock by 102.424075s
Jul 27 22:13:21 enigma ntpd[32676]: adjusting local clock by 102.314918s
Jul 27 22:17:10 enigma ntpd[32676]: adjusting local clock by 102.248247s
Jul 27 22:19:13 enigma ntpd[32676]: adjusting local clock by 102.065928s
Jul 27 19:20:04 enigma ntpd[32677]: ntp engine exiting
Jul 27 22:20:04 enigma ntpd[32676]: Terminating
Jul 27 22:20:04 enigma ntpd[1092]: listening on 192.168.3.1
Jul 27 19:20:04 enigma ntpd[1092]: ntp engine ready
Jul 27 19:20:22 enigma ntpd[1092]: peer 81.210.250.102 now valid
Jul 27 19:20:22 enigma ntpd[1092]: peer 89.25.11.9 now valid
Jul 27 19:20:23 enigma ntpd[1092]: peer 212.244.104.2 now valid
Jul 27 19:20:25 enigma ntpd[1092]: peer 139.143.5.30 now valid
Jul 27 19:20:26 enigma ntpd[1092]: peer 130.60.75.60 now valid
Jul 27 19:20:27 enigma ntpd[1092]: peer 213.239.212.133 now valid
Jul 27 19:20:30 enigma ntpd[1092]: peer 66.180.136.186 now valid
Jul 27 22:21:26 enigma ntpd[1091]: adjusting local clock by 101.912042s
Jul 27 19:24:18 enigma ntpd[1092]: ntp engine exiting
Jul 27 22:24:18 enigma ntpd[1091]: Terminating
Jul 27 22:24:18 enigma ntpd[1431]: listening on 192.168.3.1
Jul 27 19:24:18 enigma ntpd[1431]: ntp engine ready
Jul 27 19:24:37 enigma ntpd[1431]: peer 213.239.212.133 now valid
Jul 27 19:24:38 enigma ntpd[1431]: peer 212.244.104.2 now valid
Jul 27 19:24:39 enigma ntpd[1431]: peer 89.25.11.9 now valid
Jul 27 19:24:39 enigma ntpd[1431]: peer 209.11.160.7 now valid
Jul 27 19:24:41 enigma ntpd[1431]: peer 130.60.75.60 now valid
Jul 27 19:24:43 enigma ntpd[1431]: peer 81.210.250.102 now valid
Jul 27 19:24:44 enigma ntpd[1431]: peer 66.180.136.186 now valid
Jul 27 19:25:45 enigma ntpd[1431]: peer 89.25.11.9 now invalid
Jul 27 22:26:08 enigma ntpd[1430]: adjusting local clock by 101.742480s
Jul 27 19:26:24 enigma ntpd[1431]: peer 130.60.75.60 now invalid
Jul 27 19:26:54 enigma ntpd[1431]: peer 81.210.250.102 now invalid
Jul 27 22:29:46 enigma ntpd[1430]: adjusting local clock by 101.681414s
Jul 27 22:32:30 enigma ntpd[1430]: adjusting local clock by 101.532742s
Jul 27 19:34:59 enigma ntpd[1431]: peer 82.225.138.2 now valid
Jul 27 22:35:57 enigma ntpd[1430]: adjusting local clock by 101.413649s
Jul 27 19:36:58 enigma ntpd[1431]: peer 89.25.11.9 now valid
Jul 27 19:37:14 enigma ntpd[1431]: peer 130.60.75.60 now valid
Jul 27 19:37:57 enigma ntpd[1431]: peer 81.210.250.102 now valid
Jul 27 22:38:35 enigma ntpd[1430]: adjusting local clock by 101.265187s
--
best regards,
Aleksey V. Kunitskiy
my public GPG/PGP key: http://www.alexey-kv.org.ua/pubkey.asc
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-07-27 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 20:45 Aleksey V. Kunitskiy [this message]
2007-07-27 20:04 ` [gentoo-user] ntpd clock adjusting Dirk Heinrichs
2007-07-27 20:17 ` Aleksey V. Kunitskiy
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=200707272345.57903.alexey.kv@gmail.com \
--to=alexey.kv@gmail.com \
--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