Date: Tue, 6 Nov 2001 06:30:48 -0800 (PST) From: Mike Harding <mvh@ix.netcom.com> To: mikea@mikea.ath.cx Cc: stable@FreeBSD.ORG Subject: Re: ntpd problems? Message-ID: <20011106143048.03BBD13573@netcom1.netcom.com> In-Reply-To: <20011106082257.A26785@mikea.ath.cx> (message from mikea on Tue, 6 Nov 2001 08:22:57 -0600) References: <20011106141816.9F53A13573@netcom1.netcom.com> <20011106082257.A26785@mikea.ath.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
I am using a dial-up line, so it is possible that the apparent delays
can be going all over the place, but I did not see this until
recently. I notice that 'ntpd' now seems to be reporting jitter after
1 sample - this must be an error which was introduced recently...
ntpq> peers
remote refid st t when poll reach delay offset jitter
==============================================================================
usno.pa-x.dec.c .USNO. 1 u 21 64 1 1549.64 691.615 646.947
tick.ucla.edu .USNO. 1 u 20 64 1 1167.35 507.150 474.396
as how can the jitter be measured with 1 sample? This is after I
restarted ntpd...
here's another sample, after another ntpd restart...
ntpq> peers
remote refid st t when poll reach delay offset jitter
==============================================================================
usno.pa-x.dec.c .USNO. 1 u 10 64 1 129.614 -65.532 61.300
tick.ucla.edu .USNO. 1 u 9 64 1 129.504 -66.510 62.215
- Mike H.
Date: Tue, 6 Nov 2001 08:22:57 -0600
From: mikea <mikea@mikea.ath.cx>
Cc: stable@FreeBSD.ORG
Content-Disposition: inline
X-SpamBouncer: 1.4 (8/24/01)
X-SBClass: OK
On Tue, Nov 06, 2001 at 06:18:16AM -0800, Mike Harding wrote:
>
> it might be my clock, but I am suddenly seeing lots of...
>
> bash-2.05$ grep reset /var/log/messages
> Nov 3 07:35:57 netcom1 ntpd[189]: time reset 0.627666 s
> Nov 3 16:03:29 netcom1 ntpd[188]: time reset 0.370751 s
> Nov 4 05:06:01 netcom1 ntpd[185]: time reset 0.478860 s
> Nov 4 14:31:09 netcom1 ntpd[187]: time reset 0.137700 s
> Nov 4 17:37:54 netcom1 ntpd[188]: time reset 1.071828 s
> Nov 4 19:26:03 netcom1 ntpd[188]: time reset -0.318037 s
> Nov 4 19:47:37 netcom1 ntpd[188]: time reset 0.558822 s
> Nov 4 20:27:27 netcom1 ntpd[188]: time reset 1.050031 s
> Nov 5 05:05:55 netcom1 ntpd[185]: time reset 0.421592 s
> Nov 5 05:37:59 netcom1 ntpd[185]: time reset 0.257157 s
> Nov 5 12:09:58 netcom1 ntpd[185]: time reset 1.985702 s
> Nov 5 19:09:44 netcom1 ntpd[185]: time reset 0.159401 s
> Nov 5 21:02:37 netcom1 ntpd[223]: time reset 0.787817 s
> Nov 6 03:10:38 netcom1 ntpd[223]: time reset 0.201159 s
> bash-2.05$
>
> in /var/log/messages. Any ideas?
What timeservers are you using? Is the path to one or more of
them flaky and changing length or topology?
--
Mike Andrews
mikea@mikea.ath.cx
Tired old sysadmin since 1964
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011106143048.03BBD13573>