From owner-freebsd-hackers@freebsd.org Fri Oct 5 09:24:52 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D91010C7959 for ; Fri, 5 Oct 2018 09:24:52 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [194.1.144.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F446791DB for ; Fri, 5 Oct 2018 09:24:51 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.15.2/8.15.2) with ESMTPS id w959Omne009746 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 5 Oct 2018 11:24:48 +0200 (CEST) (envelope-from puchar-wojtek@puchar.net) Received: from localhost (puchar-wojtek@localhost) by puchar.net (8.15.2/8.15.2/Submit) with ESMTP id w959OhqA009743; Fri, 5 Oct 2018 11:24:43 +0200 (CEST) (envelope-from puchar-wojtek@puchar.net) Date: Fri, 5 Oct 2018 11:24:42 +0200 (CEST) From: Wojciech Puchar To: Peter Jeremy cc: Wojciech Puchar , freebsd-hackers@freebsd.org Subject: Re: ntpd strange problem In-Reply-To: <20181005061829.GG21091@server.rulingia.com> Message-ID: References: <20181005061829.GG21091@server.rulingia.com> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2018 09:24:52 -0000 >> 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