From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-185277-garchives=archives.gentoo.org@lists.gentoo.org>
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 5F31D138239
	for <garchives@archives.gentoo.org>; Fri,  2 Nov 2018 16:59:42 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 036EBE088B;
	Fri,  2 Nov 2018 16:59:35 +0000 (UTC)
Received: from smarthost03b.mail.zen.net.uk (smarthost03b.mail.zen.net.uk [212.23.1.21])
	(using TLSv1.2 with cipher DHE-RSA-AES128-SHA256 (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 89CA8E0880
	for <gentoo-user@lists.gentoo.org>; Fri,  2 Nov 2018 16:59:34 +0000 (UTC)
Received: from [82.69.80.10] (helo=peak.localnet)
	by smarthost03b.mail.zen.net.uk with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
	(Exim 4.80)
	(envelope-from <peter@prh.myzen.co.uk>)
	id 1gIcnE-0003c1-Rj
	for gentoo-user@lists.gentoo.org; Fri, 02 Nov 2018 16:59:32 +0000
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] chrony-3.3 hangs at boot
Date: Fri, 02 Nov 2018 16:59:32 +0000
Message-ID: <3560477.jXi8gUb11z@peak>
In-Reply-To: <60449A2C-8E0A-46EF-B156-2C37CB8BDD66@stellar.eclipse.co.uk>
References: <2280527.7xjltv8kMM@dell_xps> <pan$cc913$39f590a1$5ee4c7a2$4c5f6e1b@applied-asynchrony.com> <60449A2C-8E0A-46EF-B156-2C37CB8BDD66@stellar.eclipse.co.uk>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
X-Originating-smarthost03b-IP: [82.69.80.10]
Feedback-ID: 82.69.80.10
X-Archives-Salt: 19562d29-c1ce-4c5d-8717-db822a52d421
X-Archives-Hash: ad3a12c342fbb43f4df8e1f0b0ab1b36

On Friday, 2 November 2018 16:38:14 GMT Stroller wrote:
> > On 3 Sep 2018, at 19:10, Holger Hoffst=C3=A4tte <holger@applied-asynchr=
ony.com>
> > wrote:>=20
> > 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=
=2E=20
> >> The logs do not reveal anything amiss.  I suspect it waits for a netwo=
rk
> >> connection, which is not yet up when chronyd launches.
> >> =E2=80=A6
> >=20
> > 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.
> Perhaps I'm experiencing this because I'm using a Linode VM - it seems to
> hang indefinitely, not just for 90 seconds - but it looks a bit like the
> devs have passed the report upstream and left the affected versions in the
> tree to bite stable users.

It just happens on one machine here, but I shorten the wait by rattling key=
s=20
to supply entropy.

=2D-=20
Regards,
Peter.