From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matias Jose Seco Baccanelli Subject: Re: ntpd: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Date: Tue, 12 Nov 2019 21:18:51 +0100 Message-ID: <20191112211851.09da7bda.matias_jose_seco@autoproduzioni.net> References: <20191101211311.347cea33.matias_jose_seco@autoproduzioni.net> <20191103082720.586ad737.matias_jose_seco@autoproduzioni.net> <87sgmuvrrl.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/n=FZdF1Jcl9RJ+567RBvFZ0"; protocol="application/pgp-signature"; micalg=pgp-sha512 Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:54239) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iUcd7-00005d-8p for help-guix@gnu.org; Tue, 12 Nov 2019 15:19:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iUcd5-0001wQ-Vh for help-guix@gnu.org; Tue, 12 Nov 2019 15:19:12 -0500 Received: from confino.investici.org ([212.103.72.250]:59563) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iUcd5-0001qY-FR for help-guix@gnu.org; Tue, 12 Nov 2019 15:19:11 -0500 In-Reply-To: <87sgmuvrrl.fsf@gmail.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Maxim Cournoyer Cc: help-guix@gnu.org --Sig_/n=FZdF1Jcl9RJ+567RBvFZ0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Il giorno Mon, 11 Nov 2019 15:39:58 +0900 Maxim Cournoyer ha scritto: > Hello Matias, Hello! > [...] >=20 > The most likely reason to see this message (and have a wrong system > date) is that your hardware clock is wrong. This shouldn't be an > issue anymore on recent Guix, but older Guix NTP service > configuration used to refuse to update your clock if there was a > discrepancy of more than 3600 s between your hardware clock and the > system clock (the one sync'd with the NTP server). >=20 > So, either: >=20 > 1. Update your hardware clock > 2. Use a recent Guix, and let some time for the NTP service to sync > your clock. >=20 > As an alternative to 2, you could set the "allow-large-adjustment?" > field of your NTP configuration to #t manually (that's what Guix does > by default since commit 08b4a10fa6b). >=20 > HTH! >=20 > Maxim I confirm, as also Leo suggested, simply updating and reconfiguring the system with root, made the system fly back to present :). Thanks to all! Cheers, Matias --Sig_/n=FZdF1Jcl9RJ+567RBvFZ0 Content-Type: application/pgp-signature Content-Description: Firma digitale OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEETBXEV8HvexSq/UenrozJ05ms3x8FAl3LE6sACgkQrozJ05ms 3x9g+Q/9HhbO+tqx3kelGHIKKa6fy0hlNjabtqoaxbUVg83i7/c6h/4XDyODtNLv EWXHuusAFrgqpUAQYw8jnKfgl6EZKH8Js7eN51uvaaqFNN1Ndme2zJo7oDE+tZT1 poXsLHhd3/CDzQDzGu49KbQlXBqJZZ33ELogTzEv1/VpeNiLOHmQ3d0hYelPzBbc wR2GQoMavByrnJSfTT+ZmwnDjL3rOBa7wAqE09Pzbpe/CWvj4z/GsArWSJkf8aUw g6TXwmqWl8qwI6CzOHG294qZQbbpVhzT9e13jqkFGcpsFSzLGP/hbhhBzfKZtrvH 942VxtQq01zt2DGPjtUvjVzSoUiW27bkmJUHqK6qce3TZg+fpHRSbqgONrMRIEVo acYse25h2+B+VzO/QYqWdLXHfeB2MqbbbqCtT7NwLu3S6lsoe4t5pheLJv1AwpMz fnnu+CRjKetU6/HYadbrhuHbRb33vIG9XnoXQ//DnvXXNFsyKM7hgpT5x9gbsduK mGJDCndl2jWP2K0b348TH4xPcFsTSWXg4hqOqb33n+FnpC4PWDXVQsrVOKa5wfcg TzUsVytg1DkW6sDB6dj2TvF9ck+nWtnLJHei1Q6deTJyWfc6eG6WiUNtYtxX2/tW yslbKm8ymx1zh5VEKuLp58k8AB/IpTrU95lTntVrftoat9xrjLQ= =+X/p -----END PGP SIGNATURE----- --Sig_/n=FZdF1Jcl9RJ+567RBvFZ0--