On Ubuntu 16.04 Server (Kernel 4.4.0-22) it takes 2-5 minutes to initialize the "random: nonblocking pool" according to /var/log/syslog, compared to Ubuntu 14.04:
May 28 18:10:42 foo kernel: [ 277.447574] random: nonblocking pool is initialized
This happened a lot faster on Ubuntu 14.04 (Kernel 3.13.0-79):
May 27 06:28:56 foo kernel: [ 14.859194] random: nonblocking pool is initialized
I observed this on DigitalOcean VMs. It's causing trouble for Rails applications because the unicorn server seems to wait for this pool to become available before starting up.
What is a reasonable time for this initialization step?
Why would it take so much longer on Ubuntu 16.04?
Is it reasonable for an application to wait for this pool to become available or might the dependency on the pool be a bug on the application side?
"apt-get install rng-tools" which makes Ubuntu use available hardware number generators fixes this issue - the pool will be ready in 10s instead of minutes then.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With