Date: Tue, 23 Jan 2018 07:47:44 -0500 From: Robert Blayzor <rblayzor.bulk@inoc.net> To: Alan Somers <asomers@freebsd.org> Cc: FreeBSD <freebsd-stable@freebsd.org> Subject: Re: Clock occasionally jumps backwards on 11.1-RELEASE Message-ID: <B12F354D-EFA5-46B7-96EE-7DC2D6E0AC5A@inoc.net> In-Reply-To: <CAOtMX2iCkurg8HXn7KD9AbrPcDVSRN-jK4MR%2BgFMAd%2BOFEdpow@mail.gmail.com> References: <CAOtMX2iCkurg8HXn7KD9AbrPcDVSRN-jK4MR%2BgFMAd%2BOFEdpow@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 22, 2018, at 12:07 PM, Alan Somers <asomers@freebsd.org> 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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B12F354D-EFA5-46B7-96EE-7DC2D6E0AC5A>