I found a workaround how my server does not cause segmentation faults. I
get them
when i comment out the config-dir option wich i normally use. I
commented it out,
because i had problems with RBL false positives.
Is it the same in your case Ken?
Am 21.10.2010 21:36, schrieb Sam Clippinger:
> Another option, if you don't want to fill your logs with spamdyke
> debugging messages, is to enable full logging ("full-log-dir"). The
> full logs will always contain every log message from spamdyke's most
> verbose setting, even if "log-level" is set to a higher value. In other
> words, you can leave "log-level" set to "info" so your logs will stay
> the same, but the full logs will contain the "debug" messages. If
> you're willing, recompiling spamdyke to include "excessive" messages
> would be even more helpful, as it outputs data about number of bytes
> sent/received. You could then simply delete all of the full log files
> every day until you see a segfault appear in your logs.
>
> Thanks for doing this, I look forward to finding out where it's crashing.
>
> -- Sam Clipinger
>
> On 10/21/10 12:55 PM, Ken S. wrote:
>> I've seen a couple of these segfaults over the past year or two, but
>> never really thought much about them until today when I saw three of
>> them trip in a little over an hour:
>>
>> [r...@mail smtpd]# grep "segfault" /var/log/messages
>> Oct 21 12:10:17 mail kernel: spamdyke[12243]: segfault at
>> 0000007fbffbfff8 rip 0000003da6e73013 rsp 0000007fbffe75a8 error 4
>> Oct 21 12:48:29 mail kernel: spamdyke[24247]: segfault at
>> 0000007fbffbfff8 rip 0000003da6e73013 rsp 0000007fbffe75a8 error 4
>> Oct 21 13:32:40 rsmail kernel: spamdyke[5630]: segfault at
>> 0000007fbffbfff8 rip 0000003da6e73013 rsp 0000007fbffe75a8 error 4
>> [r...@mail smtpd]#
>>
>> Unfortunately, I don't know enough about segfaults to be able to
>> decipher what the output is.
>>
>> I thought maybe I would look through my qmail connection log (where
>> all the spamdyke stuff logs) and find out what happened at/around the
>> segfault happened. Sadly there is nothing in the logs at these times.
>>
>> I've just changed the "log-level" from info to debug in hopes that
>> something pertinent will get logged. If there is anything else that I
>> should do to help with this, please let me know.
>>
>> Here is some system info:
>>
>> [r...@mail smtpd]# /usr/local/bin/spamdyke --version
>> spamdyke 4.1.0+TLS+CONFIGTEST+DEBUG (C)2010 Sam Clippinger, samc (at)
>> silence (dot) org
>> ...
>> [r...@mail smtpd]# uname -a
>> Linux mail.yyy.zzz 2.6.9-89.0.18.EL #1 Wed Nov 25 06:04:37 EST 2009
>> x86_64 x86_64 x86_64 GNU/Linux
>> [r...@mail smtpd]#
>> [r...@mail smtpd]# cat /etc/redhat-release
>> Red Hat Enterprise Linux ES release 4 (Nahant Update 8)
>> [r...@mail smtpd]#
>> ... (and, yes, I'm not happy that it is a RHES4 box, but that's what I
>> have to deal with right now) ...
>>
>> -ken
>>
> _______________________________________________
> spamdyke-users mailing list
> [email protected]
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
