From owner-freebsd-stable@freebsd.org Tue Jan 23 13:34:13 2018 Return-Path: Delivered-To: freebsd-stable@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 67A5DED4501 for ; Tue, 23 Jan 2018 13:34:13 +0000 (UTC) (envelope-from rblayzor.bulk@inoc.net) Received: from cp1.c0.inoc.net (cp1.c0.inoc.net [64.246.141.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 340CA7BBD2; Tue, 23 Jan 2018 13:34:13 +0000 (UTC) (envelope-from rblayzor.bulk@inoc.net) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=inoc.net; s=default; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date: In-Reply-To:From:Subject:Mime-Version:Content-Type:Sender:Reply-To:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=na4oysyqlzHj7N315IKxsInSPXKhfzy8H1Fdn1JMUQk=; b=Azx/w0rCdpHwweARzUPq5XbTJp FRa28HYKGXEDBUaebC4PmucmAcLPiKK/LQRz9e2W9hOmBwbao8wqlXI6WHOjSXDouQ+iw+frervS1 ofbjTSd/HHzrFmy/BM7X91VlGOV3CpO+h/oFObjqGPBqqWvezGlY94K/7o9Vqp+TVEHy+Tk10/OKp gI28Hp7UFnV21dbi0A4Afwo185NbVIjA+4eH7jHuIhvEPQwCKPvGsL/RMGf8wOyxbco7VZB0Yq4Th rSLl7/S/q0UHgQtqliiSWBpJVKMH8xrf2cA1jVoHelhsYgBPuBX6tFiNh3W4jsyNtY9rZCA5zNR6n +f1dW5Xw==; Received: from pool-108-4-157-162.albyny.fios.verizon.net ([108.4.157.162]:64920 helo=[10.99.3.101]) by cp1.c0.inoc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1edxzN-0006fj-IR; Tue, 23 Jan 2018 12:47:45 +0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Clock occasionally jumps backwards on 11.1-RELEASE From: Robert Blayzor In-Reply-To: Date: Tue, 23 Jan 2018 07:47:44 -0500 Cc: FreeBSD Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Alan Somers X-Mailer: Apple Mail (2.3445.5.20) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cp1.c0.inoc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - inoc.net X-Get-Message-Sender-Via: cp1.c0.inoc.net: authenticated_id: rblayzor@inoc.net X-Authenticated-Sender: cp1.c0.inoc.net: rblayzor@inoc.net X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 13:34:13 -0000 On Jan 22, 2018, at 12:07 PM, Alan Somers wrote: >=20 > * Sometimes the jumps happen immediately after ntpd adds a new server = to > its list, but not always. >=20 > * I'm using the default ntp.conf file. >=20 > * ntpd is running on both, and it should be the only process touching = the > clock. I have a script running "ntpq -c peers" once a minute, which = shows > the offset for one server suddenly jump to a large negative number. = Then > the offsets for other servers jump to the same value, then either ntpd > fixes the clock or exits because the offset is too high. - Lose ntpd running in jails and run it only on the host. Running in the = jail is totally unnecessary. - Is this a bare metal server or VM? Lots of clock issues with VM=E2=80=99= s=E2=80=A6 - Stagger your periodic jobs on the host and the jail so they don=E2=80=99= t all run at the same time slamming the host. -- inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP: https://inoc.net/~rblayzor/