| Re: [chrony-users] Chrony vs. Linux RNG |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Mon, May 07, 2018 at 10:11:36AM -0700, Denny Page wrote:
> For what it’s worth, I got bit by this yesterday moving from 4.14.30 to 4.14.39. I had a couple servers hang for a few minutes in chrony startup. However, I also had several servers that were still hung in chrony startup after 30 minutes. Adding background fixes the issue as noted.
I've seen it now too on one of my Fedora VMs running a server for
pool.ntp.org. The systemd service has a timeout of 90 seconds and
chronyd seems to be getting killed if it takes longer to start. Not
good.
As I understand it, this affects quite a few applications and there is
still some upstream discussion related to the RNG fix. Maybe it will
sort itself out on the kernel side. If not, I think we should consider
releasing 3.3.1 with the fallback to /dev/urandom.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.