From owner-freebsd-current@freebsd.org Thu Mar 16 18:25:16 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0D4DD0F6E8 for ; Thu, 16 Mar 2017 18:25:16 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A9A81D91 for ; Thu, 16 Mar 2017 18:25:16 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id v2GIP8iu041279; Thu, 16 Mar 2017 11:25:12 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201703161825.v2GIP8iu041279@gw.catspoiler.org> Date: Thu, 16 Mar 2017 11:25:08 -0700 (PDT) From: Don Lewis Subject: Re: ntpd dies nightly on a server with jails To: ohartmann@walstatt.org cc: freebsd-current@freebsd.org In-Reply-To: <20170316181318.605a3e4f@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2017 18:25:16 -0000 On 16 Mar, O. Hartmann wrote: > Am Wed, 15 Mar 2017 13:12:37 -0700 > Cy Schubert schrieb: >> > >> > When the clock is floating that wild, in all cases ntpd isn't >> > running any mor e. >> > I try to restart with options -g and -G to adjust the time quickly >> > at the beginning, which works fine. >> >> This is disconcerting. If your clock is floating wildly without ntpd >> running there are other issues that might be at play here. At most >> the clock might drift a little, maybe a minute or two a day but not >> by a lot. Does the drift cause your clocks to run fast or slow? > > Today, I switched off ntpd on the jail-bearing host. After an hour or > so the gain of the clock wasn't apart from my DCF77 clock - at least > not within the granularity of the minutes. So I switched on ntpd > again. After a while, I checked status via "service ntpd status", and > I would bet off my ass that the result was "is running with PID XXX". > The next minute I did the same, the clock was off by almost half an > hour (always behind real time, never before!) and ntpd wasn't running. > A coincidence? I can not tell, I did a "clear" on the terminal :-( But > that was strange. I think that ntp might exit if it sees time going insane. According to this old discussion, the exit is silent: https://forum.pfsense.org/index.php?topic=53906.0