Autor: Bill Hacker Data: A: exim Assumpte: Re: [exim] Fatal: no entropy gathering module detected
Jeremiah Foster wrote:
> On Mon, 2006-01-16 at 06:20 +0800, Bill Hacker wrote:
> *SNIP*
>>- Unintended / attempted multiple invocation.
>>
>>~/exim/paniclog and ~/exim/mainlog, and /var/log/messages (or the Debian
>>equivalents)
>>should be helpful.
>>
>>If that doesn't reveal an obvious misconfiguration, you will need help
>>from Debian gurus.....
>
>
> Unfortunately there is nothing in the paniclog, it is empty. The mainlog
> mostly shows spamassassin stuff, normal deliveries and such, nothing
> noticable aside from frozen messages. /var/log/messages is quiet as a
> church mouse.
Odd. If all this is 'working', are you seeing a very high count of
child processes
along with your high CPU load?
Mis-configuration, or overly agressive use of 'delay' for pseudo-tarpitting
can cause Exim to keep a very large number of connections alive.
> I think I am going to try to install exim4 from source.
> See if that works.
>
> jeremiah
>
>
Wasn't aware there was any other (safe) way....... ;-)
That should solve the randomization problem, if only by pointing out
what is missing or mis-matched
resources as it proceeeds - or halts along the way.
That should also deliver a 'standard' Exim, with a single configure
file, not the Debian-unique odd-man-out.
Do take the time to read and apply the information furnished in the
tarball as to localization
of the pre-build configuration. Very little is required to set up for a
wide variety of environments, but
much of what is there is *essential*.