mimedefang-multiplexor crash

hi,

    i have from time to time a mimedefang-multiplexor crash. The 
mimedefang process is still here but mimedefang-multiplexor is down. 
Each time we have a :

  kernel: mimedefang[10760]: segfault at 130 ip 00007faef285c900 sp 
0000000042c200f0 error 4 in libmilter.so.1.0.1[7faef2851000+f000]

(debian lenny 64 bits)

  I wonder how we could debug this and have an automatic way to restart 
the system when it triggers. The startup script of debian does not have 
a "status" command i could use for this and using a dumb "mimedefang 
start" do not work as it see the mimedefang process and think that all 
is ok and not down so it does not start. Of course a restart could not 
be used as if it work then restarting will kill performances especialy 
every 30 minutes ^^.

   Any idea on how to prevent this ?

--

-- 

Cordialement,
Ghislain ADNET.

hi,

Re: mimedefang-multiplexor crash

On Thu, 01 Sep 2011 18:16:03 +0200
Ghislain <gadnet <at> aqueos.com> wrote:

>   kernel: mimedefang[10760]: segfault at 130 ip 00007faef285c900 sp 
> 0000000042c200f0 error 4 in libmilter.so.1.0.1[7faef2851000+f000]

That looks like a mimedefang crash, not a multiplexor crash.

How did you install?  From source?  Is your milter library
the same version MIMEDefang was compiled against?

Regards,

David.

Re: mimedefang-multiplexor crash

On Thu, 1 Sep 2011, David F. Skoll wrote:

>On Thu, 01 Sep 2011 18:16:03 +0200
>Ghislain <gadnet <at> aqueos.com> wrote:
>
>>   kernel: mimedefang[10760]: segfault at 130 ip 00007faef285c900 sp
>> 0000000042c200f0 error 4 in libmilter.so.1.0.1[7faef2851000+f000]
>
>That looks like a mimedefang crash, not a multiplexor crash.
>
>How did you install?  From source?  Is your milter library
>the same version MIMEDefang was compiled against?

This looks to me like
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527862

Bug Marked as fixed in versions sendmail/8.14.4-1 and bug closed in Dec
2010. Unfortinately was the fix not released for Debian Lenny or even
Squeeze (Squeeze was the "frozen" testing release at that time.)
Both Lenny and Squeeze ship unfixed 8.14.3 versions.

Regards,

Kees Theunissen.

--

-- 
Kees Theunissen
F.O.M.-Institute for Plasma Physics Rijnhuizen, Nieuwegein, Netherlands
E-mail: theuniss <at> rijnh.nl,  Tel: (+31|0)306096724,  Fax: (+31|0)306031204

Re: mimedefang-multiplexor crash

On Thu, 1 Sep 2011, Ghislain wrote:

>hi,
>
>    i have from time to time a mimedefang-multiplexor crash. The
>mimedefang process is still here but mimedefang-multiplexor is down.
>Each time we have a :
>
>  kernel: mimedefang[10760]: segfault at 130 ip 00007faef285c900 sp
>0000000042c200f0 error 4 in libmilter.so.1.0.1[7faef2851000+f000]
>
>(debian lenny 64 bits)
>
>  I wonder how we could debug this and have an automatic way to restart
>the system when it triggers. The startup script of debian does not have
>a "status" command i could use for this and using a dumb "mimedefang
>start" do not work as it see the mimedefang process and think that all
>is ok and not down so it does not start. Of course a restart could not
>be used as if it work then restarting will kill performances especialy
>every 30 minutes ^^.
>
>
>   Any idea on how to prevent this ?

As I wrote in my other reply in this thread I think this is the bug
reported at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527862 .
Message #47 in that thread mentions a patch that can be downloaded
from http://j-chkmail.ensmp.fr/libmilter .
The "debian-lenny/" directory at that site contains patched libmilter
debian packages for "Lenny".

Re: mimedefang-multiplexor crash

Hi Ghislain,

Am Donnerstag, den 01.09.2011, 23:51 +0200 schrieb Kees Theunissen:
> On Thu, 1 Sep 2011, Ghislain wrote:
> 
> >hi,
> >
> >    i have from time to time a mimedefang-multiplexor crash. The
> >mimedefang process is still here but mimedefang-multiplexor is down.
> >Each time we have a :
> >
> >  kernel: mimedefang[10760]: segfault at 130 ip 00007faef285c900 sp
> >0000000042c200f0 error 4 in libmilter.so.1.0.1[7faef2851000+f000]
> >
> >(debian lenny 64 bits)
> >
> >  I wonder how we could debug this and have an automatic way to restart
> >the system when it triggers. The startup script of debian does not have
> >a "status" command i could use for this and using a dumb "mimedefang
> >start" do not work as it see the mimedefang process and think that all
> >is ok and not down so it does not start. Of course a restart could not
> >be used as if it work then restarting will kill performances especialy
> >every 30 minutes ^^.
> >
> >
> >   Any idea on how to prevent this ?
> 
> As I wrote in my other reply in this thread I think this is the bug
> reported at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527862 .
> Message #47 in that thread mentions a patch that can be downloaded

mimedefang-multi crash

Hi,

I've some problems with mimedefang. When trying to send a mail the 
mailserver gives me back an error message (4.x.x)
There are some error messages in the /var/log/maillog and /var/log/messages:

Sep  2 14:39:33 sparc kernel: mimedefang-mult[2378]: segfault at 20 ip 
00000039f4c3cedb sp 00007fff8aca45f0 error 4 in 
libperl.so[39f4c00000+163000]
Sep  2 14:39:37 sparc kernel: mimedefang-mult[2379]: segfault at 20 ip 
00000039f4c3cedb sp 00007fff8aca4520 error 4 in 
libperl.so[39f4c00000+163000]

Sep  2 14:39:36 sparc mimedefang-multiplexor[2317]: Starting slave 3 
(pid 2387)
(5 running): Bringing slaves up to minSlaves (5)
Sep  2 14:39:37 sparc mimedefang-multiplexor[2317]: Slave 4 died 
prematurely --
check your filter rules
Sep  2 14:39:37 sparc mimedefang[2331]: Error from multiplexor: ERR No 
response
from slave
Sep  2 14:39:37 sparc mimedefang-multiplexor[2317]: Reap: slave 4 (pid 
2379) exi
ted due to signal 11 (SLAVE DIED UNEXPECTEDLY)
Sep  2 14:39:37 sparc mimedefang-multiplexor[2317]: Slave 4 resource 
usage: req=
2, scans=1, user=0.060, sys=0.043, nswap=0, majflt=0, minflt=3622, 
maxrss=29876,
  bi=0, bo=8

Re: mimedefang-multiplexor crash

> A quick and dirty workaround is inspecting the mail-logs and restarting
> mimedefang in case of errors.
> Something like:
>
>     tail -n100 /var/log/mail.log | \
>     grep -q 'Milter (mimedefang): to error state'&&  \
>     /etc/init.d/mimedefang restart

i will try to see if i can build it with the patch or run this cron . 
Thanks for your insight on this !

--

-- 

Cordialement,
Ghislain

> A quick and dirty workaround is inspecting the mail-logs and restarting
> mimedefang in case of errors.
> Something like:
>
>     tail -n100 /var/log/mail.log | \
>     grep -q 'Milter (mimedefang): to error state'&&  \
>     /etc/init.d/mimedefang restart

i will try to see if i can build it with the patch or run this cron . 

Re: mimedefang-multiplexor crash

Le 01/09/2011 18:58, David F. Skoll a écrit :
> On Thu, 01 Sep 2011 18:16:03 +0200
> Ghislain<gadnet <at> aqueos.com>  wrote:
>
>>    kernel: mimedefang[10760]: segfault at 130 ip 00007faef285c900 sp
>> 0000000042c200f0 error 4 in libmilter.so.1.0.1[7faef2851000+f000]
> That looks like a mimedefang crash, not a multiplexor crash.
>
> How did you install?  From source?  Is your milter library
> the same version MIMEDefang was compiled against?
>

this is the debian version i used the packages.

--

-- 

Cordialement,
Ghislain

Le 01/09/2011 18:58, David F. Skoll a écrit :
> On Thu, 01 Sep 2011 18:16:03 +0200
> Ghislain<gadnet <at> aqueos.com>  wrote:
>
>>    kernel: mimedefang[10760]: segfault at 130 ip 00007faef285c900 sp
>> 0000000042c200f0 error 4 in libmilter.so.1.0.1[7faef2851000+f000]
> That looks like a mimedefang crash, not a multiplexor crash.
>

Re: mimedefang-multiplexor crash

Hello,

thanks for your reply.
I compiled Mimedefang from source.
My Sendmail version is 8.14.5. (I compiled it from source, with libmilter)
Restarting Mimedefang does not work. Every time a SMTP connection is 
established the multiplexor crashes; though the parent proccess is still 
running...

When I try to install the Mimedefang RPM I get back this:
Warning: mimedefang-2.71-1.el6.x86_64.rpm: Header V3 RSA/SHA256 
Signature, key ID 0608b895: NOKEY
error: Failed dependencies:
         libmilter.so.1.0()(64bit) is needed by mimedefang-2.71-1.el6.x86_64
         perl(Mail::SpamAssassin) >= 1.6 is needed by 
mimedefang-2.71-1.el6.x86_64

Regards

Am 04.09.2011 11:16, schrieb Ghislain:
> Le 01/09/2011 18:58, David F. Skoll a écrit :
>> On Thu, 01 Sep 2011 18:16:03 +0200
>> Ghislain<gadnet <at> aqueos.com>  wrote:
>>
>>>    kernel: mimedefang[10760]: segfault at 130 ip 00007faef285c900 sp
>>> 0000000042c200f0 error 4 in libmilter.so.1.0.1[7faef2851000+f000]
>> That looks like a mimedefang crash, not a multiplexor crash.
>>
>> How did you install?  From source?  Is your milter library
>> the same version MIMEDefang was compiled against?

mimedefang doesn't answer after some idle time

Hi

I consistently have the problem, that mimedefang stops answering after a
minute or two idle time under Linux (Ubuntu server 10.04 LTS). A problem
i don't have under FreeBSD.

I tried it before with version 2.71, but it's still the same with
version 2.72.

I compiled it from source, using all default scripts, using the options
as following:

defang   16495  0.0  0.0  53752   936 ?        Sl   15:30   0:00
/usr/bin/mimedefang -P /var/spool/MIMEDefang/mimedefang.pid -m
/var/spool/MIMEDefang/mimedefang-multiplexor.sock -z
/var/spool/MIMEDefang -U defang -S mail -r -s -t -q -p inet:33335 <at> 0.0.0.0

defang   16542  0.0  1.1  55176 12220 ?        S    15:32   0:00
/usr/bin/mimedefang-multiplexor -p
/var/spool/MIMEDefang/mimedefang-multiplexor.pid -E -z
/var/spool/MIMEDefang -S mail -m 11 -x 22 -U defang -i 100 -b 500 -r 100
-w 0 -W 0 -R 150000 -M 200000 -q 128 -Q 120 -s
/var/spool/MIMEDefang/mimedefang-multiplexor.sock

Does anyone have a hint, what the problem might be and how/what i can
check to get this sorted out?

Many thanks for your help
-Daniel