[Mimedefang] Busy Timeout Slaves

William Parr wparr at uvic.ca
Fri Apr 9 15:54:54 EDT 2010


   Had 2 instances of busy slaves since my last post. Here is what strace said what was the cause for every busy slave I tested. They all SIGTERM after 5 minutes

A RH4 Server:

sudo md-mx-ctrl -s /var/mimedefang/mimedefangm.sock busyslaves

199 B 6935 (last=scan) (scan /var/spool/MIMEDefang/mdefang-o32F7IQD006558)

[xxxx at xxx log]$ sudo strace -p 6935

Process 6935 attached - interrupt to quit

connect(5, {sa_family=AF_FILE, path="/var/mimedefang/sophie"}, 110) = ? ERESTARTSYS (To be restarted)

--- SIGTERM (Terminated) @ 0 (0) ---

Process 6935 detached

I am assuming the sophie socket is the cause of our issue here :-)


-----Original Message-----
From: mimedefang-bounces at lists.roaringpenguin.com [mailto:mimedefang-bounces at lists.roaringpenguin.com] On Behalf Of David F. Skoll
Sent: March 31, 2010 1:29 PM
To: mimedefang at lists.roaringpenguin.com
Subject: Re: [Mimedefang] Busy Timeout Slaves

William Parr wrote:

> Sorry,  hope this makes the details more readable:

It's impossible to figure out what's going on without seeing your
filter and/or the output of "strace" on a busy slave.

strace is your best bet.  Run:

	md-mx-ctrl busyslaves

a few times.  Look for ones that seem to be stuck at the
same stage, and then strace them.  If you have CPU cycles
to spare, my money is on network problems (eg, slow DNS)
or a broken virus scanner.  You're using Sophos, I see,
and closed-source software is usually the worst offender. :)

(Oh... if the server having problems is running AIX, then
you need to use the AIX equivalent of strace, if there is one.


NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang at lists.roaringpenguin.com

More information about the MIMEDefang mailing list