Date: Mon, 8 Oct 2018 13:19:18 +0200 (CEST) From: Wojciech Puchar <wojtek@puchar.net> To: Ian Lepore <ian@freebsd.org> Cc: Wojciech Puchar <wojtek@puchar.net>, freebsd-hackers@freebsd.org Subject: Re: ntpd strange problem Message-ID: <alpine.BSF.2.20.1810081315510.26846@puchar.net> In-Reply-To: <1538855151.14264.54.camel@freebsd.org> References: <alpine.BSF.2.20.1810041557330.94038@puchar.net> <20181005061829.GG21091@server.rulingia.com> <alpine.BSF.2.20.1810051122310.9032@puchar.net> <a31ca466-3ef6-8a66-10cc-1c24cd6dc928@FreeBSD.org> <alpine.BSF.2.20.1810062041490.7470@puchar.net> <1538855151.14264.54.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>>
>> what else can i do?
>
> The original output you posted showed the time as unsynchronized when
> ntpd started up. That seems normal to me, it can't be synchronized
> until ntpd has been running for a while. In a followup message you
> seemed to say that it doesn't stay synchronized, but you haven't
> provided much info about that.
>
> What's in the logs when it become unsynchronized or when you notice the
> time is several seconds off?
after starting ntpd - it seems to be no different than upsteream time
server.
After week or so it got out of sync in spite of ntpd still running.
Strange but today (4 days after i restarted ntpd) it seems to be in sync
# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
LOCAL(0) .LOCL. 2 l 93h 64 0 0.000 0.000 0.000
*ntp.task.gda.pl 194.146.251.100 2 u 227 256 377 7.127 0.006 0.050
# ntpq -c rv
associd=0 status=0615 leap_none, sync_ntp, 1 event, clock_sync, version="ntpd 4.2.8p12-a (1)", processor="amd64",
system="FreeBSD/11.2-STABLE", leap=00, stratum=3, precision=-24, rootdelay=13.877, rootdisp=31.084, refid=153.19.250.123,
reftime=df65bb67.6caa4c22 Mon, Oct 8 2018 13:17:59.424, clock=df65bb79.e7c2ec64 Mon, Oct 8 2018 13:18:17.905, peer=60901, tc=9,
mintc=3, offset=0.065124, frequency=35.388, sys_jitter=0.000000, clk_jitter=0.044, clk_wander=0.001
my ntp.conf
rlimit memlock 512
server ntp.task.gda.pl iburst maxpoll 9
restrict ntp.task.gda.pl nomodify nopeer noquery notrap
restrict -4 default ignore
restrict -6 default ignore
restrict 127.0.0.1 nomodify nopeer notrap
restrict 10.0.0.0 mask 255.0.0.0 nomodify nopeer notrap
server 127.127.1.0
fudge 127.127.1.0 stratum 2
>
> What does the output of ntptime show when the time is drifted off?
>
> How about the output of "ntpq -p" and "ntpq -c rv"?
>
> What's in your ntp.conf?
>
> If you set sysctl kern.timecounter.stepwarnings=1, do you see any
> warnings about the clock stepping as time drifts out of sync?
>
> -- Ian
>
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1810081315510.26846>