[Mimedefang] Reap: Idle slave .. exited due to signal 11 (SLAVE DIED UNEXPECTEDLY)

[Mathew Thomas]

Hi 

We have got four mail gateways runninng Solaris 9  on Sun Fire V440
with
Sendmail 8-13.1 ,Mimedefang 2.44 , SpamAssassin 2.64 +Razor 2.61 + DCC
1.2.50, Clamav and  Uvscan.

All  four are identical in hardware, software and configuration. One of
the gateway started to log the following error message all of a sudden.
There was no changes to the system. The MX_MINIMUM=20, but the actual
number of process ( ps -ef | grep mimedefang | wc -l) is always  less
than 10 after this problem. The rest of the gateways ( three servers)
are working fine. 

Jan  5 14:49:39 its-mu-mail4.its.rmit.edu.au
mimedefang-multiplexor[1709]: [ID 389462 mail.error] Slave 2 died
prematurely -- check your filter rules
Jan  5 14:49:39 its-mu-mail4.its.rmit.edu.au mimedefang[1722]: [ID
847421 mail.error] Error from multiplexor: ERR No response from slave
Jan  5 14:49:39 its-mu-mail4.its.rmit.edu.au sendmail[6135]: [ID
801593mail.info] k053nHxp006135:
to=<guntur at otto.bf.rmit.edu.au>,delay=00:00:05, pri=30804,
stat=Please try again later
Jan  5 14:49:39 its-mu-mail4.its.rmit.edu.au
mimedefang-multiplexor[1709]: [ID 502711 mail.error] Reap: Idle slave 2
(pid 6106) exited due to signal 11 (SLAVE DIED UNEXPECTEDLY)
Jan  5 14:49:40 its-mu-mail4.its.rmit.edu.au
mimedefang-multiplexor[1709]: [ID 778059 mail.info] Starting slave 2
(pid 6222) (10 running): Bringing slaves up to minSlaves (20)


What would be the problem? There are 1000s of above messages in syslog,
but still it accepts and route mail.

Thanks
Mathew