From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 83DFC138334 for ; Mon, 3 Sep 2018 18:13:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2EE95E08D9; Mon, 3 Sep 2018 18:13:12 +0000 (UTC) Received: from blaine.gmane.org (unknown [195.159.176.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A5D48E08C3 for ; Mon, 3 Sep 2018 18:13:11 +0000 (UTC) Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1fwtJT-0001ds-Bs for gentoo-user@lists.gentoo.org; Mon, 03 Sep 2018 20:10:59 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Holger =?iso-8859-1?q?Hoffst=E4tte?= Subject: [gentoo-user] Re: chrony-3.3 hangs at boot Date: Mon, 3 Sep 2018 18:10:52 +0000 (UTC) Message-ID: References: <2280527.7xjltv8kMM@dell_xps> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@blaine.gmane.org User-Agent: Pan/0.145 (Duplicitous mercenary valetism; d7e168a git.gnome.org/pan2) X-Archives-Salt: e1ae9a6d-95af-4088-ae4b-dd0692a6e72d X-Archives-Hash: ddfa108382f1c988c613cbf3d434ed40 On Mon, 03 Sep 2018 17:48:53 +0100, Mick wrote: > I just noticed today chronyd hangs during boot for a minute and a half. The > logs do not reveal anything amiss. I suspect it waits for a network > connection, which is not yet up when chronyd launches. > > Sep 3 17:38:26 asus syslog-ng[1858]: syslog-ng starting up; version='3.13.2' > Sep 3 17:38:26 asus chronyd[1930]: chronyd version 3.3 starting (+CMDMON +NTP > +REFCLOCK +RTC -PRIVDROP +SCFILTER -SIGND +ASYNCDNS -SECHASH +IPV6 -DEBUG) > Sep 3 17:38:26 asus chronyd[1930]: Frequency -13.776 +/- 1.023 ppm read from > /var/lib/chrony/drift > Sep 3 17:38:26 asus acpid[1894]: starting up with netlink and the input layer > Sep 3 17:38:26 asus acpid[1894]: 1 rule loaded > Sep 3 17:38:26 asus acpid[1894]: waiting for events: event logging is off > Sep 3 17:40:57 asus kernel: random: crng init done > Sep 3 17:40:57 asus kernel: random: 3 urandom warning(s) missed due to > ratelimiting > Sep 3 17:40:57 asus chronyd[1930]: Loaded dump file for 10.10.10.1 > > > Have you noticed the same? > > Is there a fix/workaround for this? Yes and yes; countless people have been hit by this, I was probably the first to notice/debug it. It happens due to changes in Linux' random number generator, which is now slowly making it into older kernels as well. If you're interested in the gory details you can read about them in the thread "Chrony vs. Linux RNG" at [1] or just update to chrony-3.4rc1 which contains the "fix". Despite being an rc1 it works fine as usual, so short of applying the patch to your local build this is the easiest option. cheers, Holger [1] https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-users/2018/04/threads.html#00036