public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] chrony-3.3 hangs at boot
Date: Fri, 2 Nov 2018 16:38:14 +0000	[thread overview]
Message-ID: <60449A2C-8E0A-46EF-B156-2C37CB8BDD66@stellar.eclipse.co.uk> (raw)
In-Reply-To: <pan$cc913$39f590a1$5ee4c7a2$4c5f6e1b@applied-asynchrony.com>

[-- Attachment #1: Type: text/plain, Size: 870 bytes --]



> On 3 Sep 2018, at 19:10, Holger Hoffstätte <holger@applied-asynchrony.com> wrote:
> 
> 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.
>> … 
> 
> 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.

Stroller.


[-- Attachment #2: Type: text/html, Size: 5552 bytes --]

  parent reply	other threads:[~2018-11-02 16:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 16:48 [gentoo-user] chrony-3.3 hangs at boot Mick
2018-09-03 17:47 ` James Stevenson
2018-09-03 18:04   ` Dale
2018-09-03 18:10 ` [gentoo-user] " Holger Hoffstätte
2018-09-03 21:23   ` Mick
2018-09-03 21:47     ` Holger Hoffstätte
2018-09-04  8:35       ` Mick
2018-11-02 16:38   ` Stroller [this message]
2018-11-02 16:59     ` [gentoo-user] " Peter Humphrey
2018-11-02 17:04       ` Mick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60449A2C-8E0A-46EF-B156-2C37CB8BDD66@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox