Hello,
By your numbers it seems that your machine is able to generate random numbers at good speed. But the problem is WHEN and HOW OFTEN.
Afaik, the linux kernel waits too long to trigger the process to generate random numbers and fast paced process spawning or ssl connections could deplete pool before the process is triggered again.
This is the problem that haveged could solve. Triggering a random numbers generation at a higher threshold and at higher frequency.
http://blog-ftweedal.rhcloud.com/2014/05/more-entropy-with-haveged/
Well, it is only ONE of possible causes of your problem. Unfortunately one obscure and difficult to identify because it does not generate errors, crashes or logs. Simply slowness.
Had you checked disk latency? Does your servers have enough sasl processes?
We use Debian and did not find haveged installation issues, so you will have to search a bit more about your running errors.
Regards.
Andre Felipe
http://www.techforce.com.br
Paul Bronson <signaldeveloper@xxxxxxxxx> wrote ..
Guys,
I ran cat /dev/urandom | rngtest -c 1000
and got:
rngtest: starting FIPS tests...
rngtest: bits received from input: 20000032
rngtest: FIPS 140-2 successes: 998
rngtest: FIPS 140-2 failures: 2
rngtest: FIPS 140-2(2001-10-10) Monobit: 0
rngtest: FIPS 140-2(2001-10-10) Poker: 0
rngtest: FIPS 140-2(2001-10-10) Runs: 1
rngtest: FIPS 140-2(2001-10-10) Long run: 1
rngtest: FIPS 140-2(2001-10-10) Continuous run: 0
rngtest: input channel speed: (min=22.980; avg=501.129; max=19073.486)Mibits/s
rngtest: FIPS tests speed: (min=98.317; avg=121.603; max=131.541)Mibits/s
rngtest: Program run time: 198018 microseconds
Does this look bad to you considering all of my slow SASL auths? (no haveged is on at this point.. available entropy is between 131 - 160... pool size is default 4096.
I also tried installing haveged, which worked fine, but as soon as I started the service it said something like process dead, sub sys locked... ? Sorry, entropy is fairly new to me.