Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Oct 2018 11:24:42 +0200 (CEST)
From:      Wojciech Puchar <wojtek@puchar.net>
To:        Peter Jeremy <peter@rulingia.com>
Cc:        Wojciech Puchar <wojtek@puchar.net>, freebsd-hackers@freebsd.org
Subject:   Re: ntpd strange problem
Message-ID:  <alpine.BSF.2.20.1810051122310.9032@puchar.net>
In-Reply-To: <20181005061829.GG21091@server.rulingia.com>
References:  <alpine.BSF.2.20.1810041557330.94038@puchar.net> <20181005061829.GG21091@server.rulingia.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>> 0x2041: Clock Unsynchronized
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> It will take 5-10 minutes for ntpd to synchronise to its upstream servers.
> Until then, the clock will report that it's unsynchronised.  If "ntptime"
> is still reporting that it's unsynchronised after a long period, you will
> need to do more troubleshooting.

yes the problem is that:

after starting ntpd time is exactly fine

ntpd_sync_on_start=YES
ntpd_enable=YES


but then while ntpd works, time seems to get out of sync to the extent of 
normal RTC imprecission - in order of few seconds per day.

ntpd seems like not to update time properly.

restarting ntpd fixes time again.

what should i look at to find a source of problem



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1810051122310.9032>