public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* Re: [gentoo-user] ntpd clock adjusting
  2007-07-27 20:45 [gentoo-user] ntpd clock adjusting Aleksey V. Kunitskiy
@ 2007-07-27 20:04 ` Dirk Heinrichs
  2007-07-27 20:17   ` Aleksey V. Kunitskiy
  0 siblings, 1 reply; 3+ messages in thread
From: Dirk Heinrichs @ 2007-07-27 20:04 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 872 bytes --]

Am Freitag, 27. Juli 2007 schrieb Aleksey V. Kunitskiy:
> 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

Don't know openntpd because I'm using ntpd, but: It seems the numbers are 
decreasing, so it looks like normal operation. At some point time will be 
adjusted completely.

You may also try running ntpd with -s once at boot time before starting the 
daemon permanently.

HTH...

	Dirk

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [gentoo-user] ntpd clock adjusting
  2007-07-27 20:04 ` Dirk Heinrichs
@ 2007-07-27 20:17   ` Aleksey V. Kunitskiy
  0 siblings, 0 replies; 3+ messages in thread
From: Aleksey V. Kunitskiy @ 2007-07-27 20:17 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 787 bytes --]

On Friday 27 July 2007 23:04, Dirk Heinrichs wrote:
> Don't know openntpd because I'm using ntpd, but: It seems the numbers are
> decreasing, so it looks like normal operation. At some point time will be
> adjusted completely.
Yes, it is OK. I've just found it on openbsd.org:
"...Once your clock is accurately set, ntpd will hold it at a high degree of 
accuracy, however, if your clock is more than a few minutes off, it is highly 
recommended that you bring it to close to accurate initially, as it may take 
days or weeks to bring a very-off clock to sync. You can do this using 
the "-s" option of ntpd(8) or any other way to accurately set your system 
clock."


-- 
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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [gentoo-user] ntpd clock adjusting
@ 2007-07-27 20:45 Aleksey V. Kunitskiy
  2007-07-27 20:04 ` Dirk Heinrichs
  0 siblings, 1 reply; 3+ messages in thread
From: Aleksey V. Kunitskiy @ 2007-07-27 20:45 UTC (permalink / raw
  To: gentoo-user

[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-07-27 20:23 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-07-27 20:45 [gentoo-user] ntpd clock adjusting Aleksey V. Kunitskiy
2007-07-27 20:04 ` Dirk Heinrichs
2007-07-27 20:17   ` Aleksey V. Kunitskiy

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox