Author: Heiko Schlittermann Date: To: exim-users Subject: Re: [exim] Spool file is locked (another process is handling this
message)
Yan Seiner <yan@???> (Do 12 Apr 2012 16:52:08 CEST): >
> Seems to be a TLS entropy issue? (I'm guessing here but from reading what
> I've been able to it looks similar.)
>
> Yesterday the messages were persisting for hours, and there was upwards of
> 100 stalled at a time.
>
> Not sure what I can do to help the entropy issue. It may just be that
> I've had a huge rsync job running for days and if it's using the same pool
> it could be draining all the entropy faster than the system can generate
> it. I don't know enough about how entropy works to make more than guesses
> from googling....
>
If it is entropy related, you might see the processes hanging during
read from /dev/random (use strace -p to check this)
For short term checks you could link /dev/random to /dev/urandom (or use
mknod to create a /dev/random with the same major/minor as /dev/urandom).
But on Linux /dev/ is a RAM disk maintained by udev and partly filled
at system startup.
On Linux we solved the entropy issue using the rng-tools package and put
there "/dev/urandom" as source for additional entropy.
