1 |
On Mon, 03 Sep 2018 17:48:53 +0100, Mick wrote: |
2 |
|
3 |
> I just noticed today chronyd hangs during boot for a minute and a half. The |
4 |
> logs do not reveal anything amiss. I suspect it waits for a network |
5 |
> connection, which is not yet up when chronyd launches. |
6 |
> |
7 |
> Sep 3 17:38:26 asus syslog-ng[1858]: syslog-ng starting up; version='3.13.2' |
8 |
> Sep 3 17:38:26 asus chronyd[1930]: chronyd version 3.3 starting (+CMDMON +NTP |
9 |
> +REFCLOCK +RTC -PRIVDROP +SCFILTER -SIGND +ASYNCDNS -SECHASH +IPV6 -DEBUG) |
10 |
> Sep 3 17:38:26 asus chronyd[1930]: Frequency -13.776 +/- 1.023 ppm read from |
11 |
> /var/lib/chrony/drift |
12 |
> Sep 3 17:38:26 asus acpid[1894]: starting up with netlink and the input layer |
13 |
> Sep 3 17:38:26 asus acpid[1894]: 1 rule loaded |
14 |
> Sep 3 17:38:26 asus acpid[1894]: waiting for events: event logging is off |
15 |
> Sep 3 17:40:57 asus kernel: random: crng init done |
16 |
> Sep 3 17:40:57 asus kernel: random: 3 urandom warning(s) missed due to |
17 |
> ratelimiting |
18 |
> Sep 3 17:40:57 asus chronyd[1930]: Loaded dump file for 10.10.10.1 |
19 |
> |
20 |
> |
21 |
> Have you noticed the same? |
22 |
> |
23 |
> Is there a fix/workaround for this? |
24 |
|
25 |
Yes and yes; countless people have been hit by this, I was probably the first |
26 |
to notice/debug it. It happens due to changes in Linux' random number |
27 |
generator, which is now slowly making it into older kernels as well. |
28 |
|
29 |
If you're interested in the gory details you can read about them |
30 |
in the thread "Chrony vs. Linux RNG" at [1] or just update to chrony-3.4rc1 |
31 |
which contains the "fix". Despite being an rc1 it works fine as usual, |
32 |
so short of applying the patch to your local build this is the easiest |
33 |
option. |
34 |
|
35 |
cheers, |
36 |
Holger |
37 |
|
38 |
[1] https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-users/2018/04/threads.html#00036 |