Date: Sat, 06 Oct 2018 13:45:51 -0600 From: Ian Lepore <ian@freebsd.org> To: Wojciech Puchar <wojtek@puchar.net> Cc: freebsd-hackers@freebsd.org Subject: Re: ntpd strange problem Message-ID: <1538855151.14264.54.camel@freebsd.org> In-Reply-To: <alpine.BSF.2.20.1810062041490.7470@puchar.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2018-10-06 at 20:43 +0200, Wojciech Puchar wrote: > > > > > > > > what should i look at to find a source of problem > > Is this a virtual machine or bare metal? VMs tend to have a lot > > more > bare metal. > > > > > > > driftfile /var/db/ntpd.drift > > > > then ntpd will record how fast or slow the clock tends to run so it > > can > > immediately account for that across restarts, rather than having to > > work it > > out de-novo everytime ntpd gets restarted. > > > # cat /var/db/ntpd.drift > 35.586 > > 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? 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1538855151.14264.54.camel>