From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: chrony-3.3 hangs at boot
Date: Mon, 3 Sep 2018 18:10:52 +0000 (UTC) [thread overview]
Message-ID: <pan$cc913$39f590a1$5ee4c7a2$4c5f6e1b@applied-asynchrony.com> (raw)
In-Reply-To: 2280527.7xjltv8kMM@dell_xps
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
next prev parent reply other threads:[~2018-09-03 18:13 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 ` Holger Hoffstätte [this message]
2018-09-03 21:23 ` [gentoo-user] " Mick
2018-09-03 21:47 ` Holger Hoffstätte
2018-09-04 8:35 ` Mick
2018-11-02 16:38 ` [gentoo-user] " Stroller
2018-11-02 16:59 ` 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='pan$cc913$39f590a1$5ee4c7a2$4c5f6e1b@applied-asynchrony.com' \
--to=holger@applied-asynchrony.com \
--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