From owner-freebsd-hackers@freebsd.org Wed Oct 10 11:10:54 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 55C5A10D004D for ; Wed, 10 Oct 2018 11:10:54 +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 CBFCC7AAC5; Wed, 10 Oct 2018 11:10:53 +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 w9ABAhfk036188 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 10 Oct 2018 13:10:43 +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 w9ABAcjg036185; Wed, 10 Oct 2018 13:10:38 +0200 (CEST) (envelope-from puchar-wojtek@puchar.net) Date: Wed, 10 Oct 2018 13:10:38 +0200 (CEST) From: Wojciech Puchar To: Ian Lepore cc: Wojciech Puchar , Peter Jeremy , freebsd-hackers@freebsd.org Subject: Re: ntpd strange problem In-Reply-To: <1539093981.72469.30.camel@freebsd.org> Message-ID: References: <20181005061829.GG21091@server.rulingia.com> <1538855151.14264.54.camel@freebsd.org> <20181009052924.GJ21091@server.rulingia.com> <1539093981.72469.30.camel@freebsd.org> 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: Wed, 10 Oct 2018 11:10:54 -0000 >>> useful. >> this server is quite (actually excellently) stable and i trust it. > > When I asked for various outputs, I meant "when the unsync problem is > happening"; those outputs are uninteresting when everything is working > right. so i will look back and tell you WHEN it will happen again. > > You should remove the config for the "local" clock from your ntp.conf. > Configuring a bogus local clock is NEVER the right thing to do, and > it's even worse to configure it at a high stratum number. thank you. this is an error.