From owner-freebsd-hackers@freebsd.org Fri Oct 5 06:18:49 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 C844610C37F1 for ; Fri, 5 Oct 2018 06:18:49 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vtr.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F2ED7731B5 for ; Fri, 5 Oct 2018 06:18:48 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp59-167-167-3.static.internode.on.net [59.167.167.3]) by vtr.rulingia.com (8.15.2/8.15.2) with ESMTPS id w956IZue018156 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 5 Oct 2018 16:18:42 +1000 (AEST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id w956IT0u099627 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 5 Oct 2018 16:18:29 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id w956ITxX099626; Fri, 5 Oct 2018 16:18:29 +1000 (AEST) (envelope-from peter) Date: Fri, 5 Oct 2018 16:18:29 +1000 From: Peter Jeremy To: Wojciech Puchar Cc: freebsd-hackers@freebsd.org Subject: Re: ntpd strange problem Message-ID: <20181005061829.GG21091@server.rulingia.com> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="4ZLFUWh1odzi/v6L" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.10.0 (2018-05-17) 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 06:18:50 -0000 --4ZLFUWh1odzi/v6L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2018-Oct-04 15:58:26 +0200, Wojciech Puchar wrote: >what does message mean and how to fix it? >----- >Oct 4 15:56:46 <12.5> puchar ntpd[93928]: ntpd 4.2.8p12-a (1): Starting =2E.. >Oct 4 15:56:46 <12.6> puchar ntpd[93929]: kernel reports TIME_ERROR:=20 >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. --=20 Peter Jeremy --4ZLFUWh1odzi/v6L Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAlu3AjVfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi CzTDgw/+OPwUjNT/cCXw8Jc0FKsYlg88ZZLAl1QZxXdL0CWrfpXdeuwbWKwcwiO9 RQTDU04nlC/y3ryiUZKJXB5etzdPLnzzICupyCTzImb9fJ46b9DyHxgwgeBpOxAW JpufIjpND2eYS9WM78rTUC/HNJt7PSwwkwHtodZMo6c2GGzpc5n+35/6uWNaWVDP zIzvfuW36Y0q2zl/A7npHnbKBwTFsWcJ/urCEA1ojbmZUPj18O3XQSVLhb/iQ3H4 DFT8uPpvwshjsTTZ0uP5x1MIT+ivKw5wpO2Y7+xOKn3pZ2lYCVzRVMwf9jIXR5/P 5sGDsaUI4bAx29DZL0oCycllfrbpkvn/FwvujD+215zH4sTvtR/w5ztCVk49RKm4 pHMGJac6QwwL0Y8ww6Rs7PZy9KLnIWI5hGiX+IK1mQXXn7VB0lqgWIyYp7RTO1RX XseLsXmQP9NNt4vGcsp6bMN53GvW+/IiN8hr1/qFSkjy/NfiFONvwgrH0HPdV+cn mfLGhmfRQoIEUt1+s7F3a5c9L8BAlGH8m6ZYkkGBQKteSWB/luEscAcdc6QK8p3n RBsXIRb8aRXOblkfQ2TQ3B64WWwq3Y02//9gOuIosvJGhPhD95t5Jj1z3rw3cbkW 8/vjnE+x1+zogi/tp8jtQJR7mBrS/INObqBmlGS99Wf4HuyTmUw= =bkvk -----END PGP SIGNATURE----- --4ZLFUWh1odzi/v6L--