Re: [spamdyke-users] Segfault in spamdyke (libc-2.14.1.so) since use of version 5 | *** glibc detected *** /usr/local/bin/spamdyke: double free or corruption (fasttop):

[Webtao via spamdyke-users]

Thank you Sam,
In fact, since my Centos update, I also had an issue with Roudcube, I could not 
send email. So I took back the previous version of Roundcube and there was no 
bug anymore on my VPS.
So cool!

It was nice to help me :-)

Bye, Lenawaii

> Le 1 avr. 2020 à 15:12, Sam Clippinger via spamdyke-users 
>  a écrit :
> 
> H looks like a bug, but because spamdyke is compiled C, there's 
> almost no way to tell how it happened.  If you updated your OS but didn't 
> update spamdyke, I'd suggest making sure you're on the latest version of 
> spamdyke and recompiling it on your updated OS.  If you still see crashes, 
> the best way to troubleshoot them would be to find a reliable way to 
> reproduce them -- using spamdyke's "full-log-dir" option to capture the 
> input, for example.  Failing that, I could send you some updates for your 
> Makefile to recompile spamdyke with an address sanitizer that will produce 
> must larger (and much more informative) crash messages.
> 
> -- Sam Clippinger
> 
> 
> 
> 
>> On Mar 30, 2020, at 7:51 PM, Webtao via spamdyke-users 
>> mailto:spamdyke-users@spamdyke.org>> wrote:
>> 
>> Hi Sam,
>> 
>> First of all, thank you for managing spamdyke :-)
>> 
>> Lately, I updated my Centos 6.5 and suddenly got this error :
>> 
>> *** glibc detected *** /usr/bin/spamdyke: double free or corruption 
>> (fasttop): 0x0127afe0 ***
>> === Backtrace: =
>> /lib64/libc.so.6(+0x75e5e)[0x7fad8a556e5e]
>> /lib64/libc.so.6(+0x78cad)[0x7fad8a559cad]
>> /usr/bin/spamdyke[0x41e7f7]
>> /usr/bin/spamdyke[0x41797e]
>> /lib64/libc.so.6(__libc_start_main+0x100)[0x7fad8a4ffd20]
>> /usr/bin/spamdyke[0x402849]
>> 
>> Do you have any idea to resolve this?
>> 
>> Thank you for your help, Lenawaii
>> ___
>> spamdyke-users mailing list
>> spamdyke-users@spamdyke.org 
>> https://spamdyke.org/mailman/listinfo/spamdyke-users
> 
> ___
> spamdyke-users mailing list
> spamdyke-users@spamdyke.org
> https://spamdyke.org/mailman/listinfo/spamdyke-users

___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
https://spamdyke.org/mailman/listinfo/spamdyke-users

Re: [spamdyke-users] Segfault in spamdyke (libc-2.14.1.so) since use of version 5 | *** glibc detected *** /usr/local/bin/spamdyke: double free or corruption (fasttop):

[Sam Clippinger via spamdyke-users]

H looks like a bug, but because spamdyke is compiled C, there's almost 
no way to tell how it happened.  If you updated your OS but didn't update 
spamdyke, I'd suggest making sure you're on the latest version of spamdyke and 
recompiling it on your updated OS.  If you still see crashes, the best way to 
troubleshoot them would be to find a reliable way to reproduce them -- using 
spamdyke's "full-log-dir" option to capture the input, for example.  Failing 
that, I could send you some updates for your Makefile to recompile spamdyke 
with an address sanitizer that will produce must larger (and much more 
informative) crash messages.

-- Sam Clippinger




> On Mar 30, 2020, at 7:51 PM, Webtao via spamdyke-users 
>  wrote:
> 
> Hi Sam,
> 
> First of all, thank you for managing spamdyke :-)
> 
> Lately, I updated my Centos 6.5 and suddenly got this error :
> 
> *** glibc detected *** /usr/bin/spamdyke: double free or corruption 
> (fasttop): 0x0127afe0 ***
> === Backtrace: =
> /lib64/libc.so.6(+0x75e5e)[0x7fad8a556e5e]
> /lib64/libc.so.6(+0x78cad)[0x7fad8a559cad]
> /usr/bin/spamdyke[0x41e7f7]
> /usr/bin/spamdyke[0x41797e]
> /lib64/libc.so.6(__libc_start_main+0x100)[0x7fad8a4ffd20]
> /usr/bin/spamdyke[0x402849]
> 
> Do you have any idea to resolve this?
> 
> Thank you for your help, Lenawaii
> ___
> spamdyke-users mailing list
> spamdyke-users@spamdyke.org
> https://spamdyke.org/mailman/listinfo/spamdyke-users

___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
https://spamdyke.org/mailman/listinfo/spamdyke-users

[spamdyke-users] Segfault in spamdyke (libc-2.14.1.so) since use of version 5 | *** glibc detected *** /usr/local/bin/spamdyke: double free or corruption (fasttop):

[Webtao via spamdyke-users]

Hi Sam,

First of all, thank you for managing spamdyke :-)

Lately, I updated my Centos 6.5 and suddenly got this error :

*** glibc detected *** /usr/bin/spamdyke: double free or corruption (fasttop): 
0x0127afe0 ***
=== Backtrace: =
/lib64/libc.so.6(+0x75e5e)[0x7fad8a556e5e]
/lib64/libc.so.6(+0x78cad)[0x7fad8a559cad]
/usr/bin/spamdyke[0x41e7f7]
/usr/bin/spamdyke[0x41797e]
/lib64/libc.so.6(__libc_start_main+0x100)[0x7fad8a4ffd20]
/usr/bin/spamdyke[0x402849]

Do you have any idea to resolve this?

Thank you for your help, Lenawaii
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
https://spamdyke.org/mailman/listinfo/spamdyke-users

Re: [spamdyke-users] Segfault in spamdyke (libc-2.14.1.so) since use of version 5 | *** glibc detected *** /usr/local/bin/spamdyke: double free or corruption (fasttop):

[Sam Clippinger via spamdyke-users]

Well, dang!  I'll keep hunting for more bugs, but if you have a way to trigger 
these crashes reliably, I'd really love to work with you to get access so I can 
test directly.  If the version of gcc is new enough, I'd want to try 
recompiling spamdyke with the -fsanitize=address flag, which will provide a ton 
more information about these crashes.  Failing that, I would want to recompile 
spamdyke to insert a bunch more logging statements (to try to find the 
function/line that is causing the crash).  The first would work even on a 
production server, but the latter approach probably would not.

-- Sam Clippinger




On Apr 13, 2015, at 3:46 AM, Konstantin via spamdyke-users 
 wrote:

> Unfortunately after about four hours I'm seeing segfaults in my logs again. 
> :( I found it strange that it didn't happened right away after installing a 
> new spamdyke version.
> 
> ...
> Apr 13 11:31:11 mail kernel: spamdyke[26755]: segfault at 11 ip 
> 7fbe85b03828 sp 7fff69e76990 error 4 in 
> libc-2.20.so[7fbe85ab9000+18f000]
> Apr 13 11:31:12 mail kernel: spamdyke[26757]: segfault at 11 ip 
> 7f58fb0ad828 sp 7fffc4458310 error 4 in 
> libc-2.20.so[7f58fb063000+18f000]
> Apr 13 11:31:14 mail kernel: spamdyke[26852]: segfault at 11 ip 
> 7fccb8c5e828 sp 7fffc7f75680 error 4 in 
> libc-2.20.so[7fccb8c14000+18f000]
> Apr 13 11:31:30 mail kernel: spamdyke[27029]: segfault at 11 ip 
> 7fe3c1cf2828 sp 7fff02d8dbe0 error 4 in 
> libc-2.20.so[7fe3c1ca8000+18f000]
> Apr 13 11:31:44 mail kernel: spamdyke[27195]: segfault at 11 ip 
> 7fa9c03f7828 sp 7fff603a84a0 error 4 in 
> libc-2.20.so[7fa9c03ad000+18f000]
> Apr 13 11:31:44 mail kernel: spamdyke[27194]: segfault at 11 ip 
> 7f26ce2e3828 sp 7fffd0e82ad0 error 4 in 
> libc-2.20.so[7f26ce299000+18f000]
> Apr 13 11:32:09 mail kernel: spamdyke[27473]: segfault at 11 ip 
> 7f9cb6c8b828 sp 7fff98b69090 error 4 in 
> libc-2.20.so[7f9cb6c41000+18f000]
> Apr 13 11:32:10 mail kernel: spamdyke[27512]: segfault at 11 ip 
> 7f211777f828 sp 7fffb6cfaf00 error 4 in 
> libc-2.20.so[7f2117735000+18f000]
> Apr 13 11:32:36 mail kernel: spamdyke[27704]: segfault at 11 ip 
> 7f8565bf6828 sp 7fff13651420 error 4 in 
> libc-2.20.so[7f8565bac000+18f000]
> Apr 13 11:32:43 mail kernel: spamdyke[27829]: segfault at 11 ip 
> 7f8752792828 sp 7fff05047470 error 4 in 
> libc-2.20.so[7f8752748000+18f000]
> ...
> 
> Let me know if I can help you to debug this issue.
> 
> BR,
> Konstantin
> 
> 
> On 2015-04-12 17:16, Konstantin via spamdyke-users wrote:
>> LOL. I think it even has a graphic installer in our days. Which I
>> never used actually. :) If you need a test environment I can always
>> make one for you.
>> Your patch is working, I think. I don't see kernel general protection
>> errors in logs anymore. So I assume that problem in my case is fixed.
>> The only one that bothers me now is that spamdyke-qrv fails to check
>> valid recipients for aliased domain forwards. So to make that work now
>> I have to create an additional duplicate forwards for these aliased
>> domains as workaround. Everything else is just great. :) Thank you.
>> BR,
>> Konstantin
>> On 2015-04-12 11:13, Sam Clippinger via spamdyke-users wrote:
>>> Wow Gentoo, really? Every time I consider Gentoo, I start getting
>>> flashbacks of installing Slackware 1.2 from floppy disks back in the
>>> elder days. Nevertheless, I tried installing Gentoo to try to
>>> duplicate your environment and gave up about halfway through the
>>> install guide... I can't remember how far I got, but it was one of the
>>> pages in the low 500's, I think. :)
>>> Anyway, I've spent the last couple days hunting bugs and I've found a
>>> few that might be responsible for these errors. Could you try applying
>>> this patch and see if it resolves the segfaults? It should apply
>>> cleanly to spamdyke 5.0.0:
>>> cd /path/to/src/spamdyke-5.0.0
>>> patch -p1 < spamdyke-5.0.0-segfault.patch
>>> make
>>> Then install the new binary over the old one.
>>> If this doesn't fix your crashes, at least it'll fix a lot of other
>>> potential ones!
>>> -- Sam Clippinger
>>> On Apr 9, 2015, at 11:05 PM, Konstantin via spamdyke-users
>>>  wrote:
 Hi Everyone!
 On a virtual gentoo server I currently have:
 ebuild: dev-libs/openssl-1.0.1l-r1
 OpenSSL 1.0.1l 15 Jan 2015
 ebuild: sys-devel/gcc-4.8.4
 gcc (Gentoo 4.8.4 p1.4, pie-0.6.1) 4.8.4
 ebuild: sys-libs/glibc-2.20-r2
 glibc 2.20
 ebuild: sys-kernel/gentoo-sources-3.17.7
 custom build kernel 3.17.7-gentoo-domU
 Not sure about /etc/xinetd.d/smtps_psa since I don't have it but
 unning process looks like this:
 10821 ? S 4:07 /usr/bin/tcpserver -p -v -R -x
 /etc/tcprules.d/tcp.qmail-smtp.cdb -c 40 -u 201 -g 200 0.0.0.0 smtp
 spamdyke -f /etc/spamdyke/spamdyke.conf /var/qmail/bin/qmail-smtpd
 /var/vpopmail/bin/vchkpw /bin/true
 Let me know if I can provide you something more relevant, Sam.

Re: [spamdyke-users] Segfault in spamdyke (libc-2.14.1.so) since use of version 5 | *** glibc detected *** /usr/local/bin/spamdyke: double free or corruption (fasttop):

[Konstantin via spamdyke-users]

Unfortunately after about four hours I'm seeing segfaults in my logs 
again. :( I found it strange that it didn't happened right away after 
installing a new spamdyke version.


...
Apr 13 11:31:11 mail kernel: spamdyke[26755]: segfault at 11 ip 
7fbe85b03828 sp 7fff69e76990 error 4 in 
libc-2.20.so[7fbe85ab9000+18f000]
Apr 13 11:31:12 mail kernel: spamdyke[26757]: segfault at 11 ip 
7f58fb0ad828 sp 7fffc4458310 error 4 in 
libc-2.20.so[7f58fb063000+18f000]
Apr 13 11:31:14 mail kernel: spamdyke[26852]: segfault at 11 ip 
7fccb8c5e828 sp 7fffc7f75680 error 4 in 
libc-2.20.so[7fccb8c14000+18f000]
Apr 13 11:31:30 mail kernel: spamdyke[27029]: segfault at 11 ip 
7fe3c1cf2828 sp 7fff02d8dbe0 error 4 in 
libc-2.20.so[7fe3c1ca8000+18f000]
Apr 13 11:31:44 mail kernel: spamdyke[27195]: segfault at 11 ip 
7fa9c03f7828 sp 7fff603a84a0 error 4 in 
libc-2.20.so[7fa9c03ad000+18f000]
Apr 13 11:31:44 mail kernel: spamdyke[27194]: segfault at 11 ip 
7f26ce2e3828 sp 7fffd0e82ad0 error 4 in 
libc-2.20.so[7f26ce299000+18f000]
Apr 13 11:32:09 mail kernel: spamdyke[27473]: segfault at 11 ip 
7f9cb6c8b828 sp 7fff98b69090 error 4 in 
libc-2.20.so[7f9cb6c41000+18f000]
Apr 13 11:32:10 mail kernel: spamdyke[27512]: segfault at 11 ip 
7f211777f828 sp 7fffb6cfaf00 error 4 in 
libc-2.20.so[7f2117735000+18f000]
Apr 13 11:32:36 mail kernel: spamdyke[27704]: segfault at 11 ip 
7f8565bf6828 sp 7fff13651420 error 4 in 
libc-2.20.so[7f8565bac000+18f000]
Apr 13 11:32:43 mail kernel: spamdyke[27829]: segfault at 11 ip 
7f8752792828 sp 7fff05047470 error 4 in 
libc-2.20.so[7f8752748000+18f000]

...

Let me know if I can help you to debug this issue.

BR,
Konstantin


On 2015-04-12 17:16, Konstantin via spamdyke-users wrote:

LOL. I think it even has a graphic installer in our days. Which I
never used actually. :) If you need a test environment I can always
make one for you.

Your patch is working, I think. I don't see kernel general protection
errors in logs anymore. So I assume that problem in my case is fixed.

The only one that bothers me now is that spamdyke-qrv fails to check
valid recipients for aliased domain forwards. So to make that work now
I have to create an additional duplicate forwards for these aliased
domains as workaround. Everything else is just great. :) Thank you.

BR,
Konstantin

On 2015-04-12 11:13, Sam Clippinger via spamdyke-users wrote:

Wow Gentoo, really? Every time I consider Gentoo, I start getting
flashbacks of installing Slackware 1.2 from floppy disks back in the
elder days. Nevertheless, I tried installing Gentoo to try to
duplicate your environment and gave up about halfway through the
install guide... I can't remember how far I got, but it was one of the
pages in the low 500's, I think. :)

Anyway, I've spent the last couple days hunting bugs and I've found a
few that might be responsible for these errors. Could you try applying
this patch and see if it resolves the segfaults? It should apply
cleanly to spamdyke 5.0.0:
 cd /path/to/src/spamdyke-5.0.0
 patch -p1 < spamdyke-5.0.0-segfault.patch
 make
Then install the new binary over the old one.

If this doesn't fix your crashes, at least it'll fix a lot of other
potential ones!


-- Sam Clippinger

On Apr 9, 2015, at 11:05 PM, Konstantin via spamdyke-users
 wrote:


Hi Everyone!

On a virtual gentoo server I currently have:

ebuild: dev-libs/openssl-1.0.1l-r1
OpenSSL 1.0.1l 15 Jan 2015

ebuild: sys-devel/gcc-4.8.4
gcc (Gentoo 4.8.4 p1.4, pie-0.6.1) 4.8.4

ebuild: sys-libs/glibc-2.20-r2
glibc 2.20

ebuild: sys-kernel/gentoo-sources-3.17.7
custom build kernel 3.17.7-gentoo-domU

Not sure about /etc/xinetd.d/smtps_psa since I don't have it but
unning process looks like this:
10821 ? S 4:07 /usr/bin/tcpserver -p -v -R -x
/etc/tcprules.d/tcp.qmail-smtp.cdb -c 40 -u 201 -g 200 0.0.0.0 smtp
spamdyke -f /etc/spamdyke/spamdyke.conf /var/qmail/bin/qmail-smtpd
/var/vpopmail/bin/vchkpw /bin/true

Let me know if I can provide you something more relevant, Sam.

--
BR,
Konstantin

On 2015-04-09 20:27, Sam Clippinger via spamdyke-users wrote:
I've been looking through the many log files you sent, thank for
being
so thorough! From what I can see in the files you and Konstantin
have
sent, it looks like the problem lies somewhere in the TLS/SSL
cleanup
routine. In your log files, all of the crashes seem to happen just
after a client fails to connect with SMTPS due to a cipher
negotiation
problem. There are only four different OpenSSL error codes being
logged, which translate as:
error:1406B0CB:SSL routines:GET_CLIENT_MASTER_KEY:peer error no
cipher
error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher
error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol
version
Those appear to be the only connections that are crashing, other
connections that successfully negotiate their TLS/SSL sessions seem
to
be fine.
I haven't

Re: [spamdyke-users] Segfault in spamdyke (libc-2.14.1.so) since use of version 5 | *** glibc detected *** /usr/local/bin/spamdyke: double free or corruption (fasttop):

[Konstantin via spamdyke-users]

LOL. I think it even has a graphic installer in our days. Which I never 
used actually. :) If you need a test environment I can always make one 
for you.


Your patch is working, I think. I don't see kernel general protection 
errors in logs anymore. So I assume that problem in my case is fixed.


The only one that bothers me now is that spamdyke-qrv fails to check 
valid recipients for aliased domain forwards. So to make that work now I 
have to create an additional duplicate forwards for these aliased 
domains as workaround. Everything else is just great. :) Thank you.


BR,
Konstantin

On 2015-04-12 11:13, Sam Clippinger via spamdyke-users wrote:

Wow Gentoo, really? Every time I consider Gentoo, I start getting
flashbacks of installing Slackware 1.2 from floppy disks back in the
elder days. Nevertheless, I tried installing Gentoo to try to
duplicate your environment and gave up about halfway through the
install guide... I can't remember how far I got, but it was one of the
pages in the low 500's, I think. :)

Anyway, I've spent the last couple days hunting bugs and I've found a
few that might be responsible for these errors. Could you try applying
this patch and see if it resolves the segfaults? It should apply
cleanly to spamdyke 5.0.0:
 cd /path/to/src/spamdyke-5.0.0
 patch -p1 < spamdyke-5.0.0-segfault.patch
 make
Then install the new binary over the old one.

If this doesn't fix your crashes, at least it'll fix a lot of other
potential ones!


-- Sam Clippinger

On Apr 9, 2015, at 11:05 PM, Konstantin via spamdyke-users
 wrote:


Hi Everyone!

On a virtual gentoo server I currently have:

ebuild: dev-libs/openssl-1.0.1l-r1
OpenSSL 1.0.1l 15 Jan 2015

ebuild: sys-devel/gcc-4.8.4
gcc (Gentoo 4.8.4 p1.4, pie-0.6.1) 4.8.4

ebuild: sys-libs/glibc-2.20-r2
glibc 2.20

ebuild: sys-kernel/gentoo-sources-3.17.7
custom build kernel 3.17.7-gentoo-domU

Not sure about /etc/xinetd.d/smtps_psa since I don't have it but
unning process looks like this:
10821 ? S 4:07 /usr/bin/tcpserver -p -v -R -x
/etc/tcprules.d/tcp.qmail-smtp.cdb -c 40 -u 201 -g 200 0.0.0.0 smtp
spamdyke -f /etc/spamdyke/spamdyke.conf /var/qmail/bin/qmail-smtpd
/var/vpopmail/bin/vchkpw /bin/true

Let me know if I can provide you something more relevant, Sam.

--
BR,
Konstantin

On 2015-04-09 20:27, Sam Clippinger via spamdyke-users wrote:
I've been looking through the many log files you sent, thank for
being
so thorough! From what I can see in the files you and Konstantin
have
sent, it looks like the problem lies somewhere in the TLS/SSL
cleanup
routine. In your log files, all of the crashes seem to happen just
after a client fails to connect with SMTPS due to a cipher
negotiation
problem. There are only four different OpenSSL error codes being
logged, which translate as:
error:1406B0CB:SSL routines:GET_CLIENT_MASTER_KEY:peer error no
cipher
error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher
error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol
version
Those appear to be the only connections that are crashing, other
connections that successfully negotiate their TLS/SSL sessions seem
to
be fine.
I haven't had any success in reproducing this bug yet, but I'm still
working on it. I'm curious about some of the versions on your server
though -- could you send me the version numbers of OpenSSL, gcc and
the kernel you're running? Could you also send me your
/etc/xinetd.d/smtps_psa file (the one that starts spamdyke for
SMTPS)?
I'd like to see how it's being started so I can try to simulate it.
Thanks!
-- Sam Clippinger
On Apr 7, 2015, at 5:44 PM, Dirk via spamdyke-users
 wrote:
Dear Sam,
at first thank you for glorious work with spamdyke! I'm using it
since
several years and it's very helpful to me.
At 30th march 2015 I've done an upgrade to version 5 (previous: last
4
version). Since then I often get a segfault in spamdyke:
Tue Apr 7 12:05:19 2015] spamdyke[13607]: segfault at 14 ip
7f60ce1e3ba8 sp 7fff6bac3ce0 error 4 in
libc-2.14.1.so[7f60ce19b000+187000]
[Tue Apr 7 12:16:20 2015] spamdyke[13959]: segfault at 14 ip
7fe1145bdba8 sp 7fffa6426b90 error 4 in
libc-2.14.1.so[7fe114575000+187000]
[Tue Apr 7 12:47:31 2015] spamdyke[15309]: segfault at 14 ip
7f9971e49ba8 sp 7fffa03aad20 error 4 in
libc-2.14.1.so[7f9971e01000+187000]
[Tue Apr 7 15:30:51 2015] spamdyke[21795]: segfault at 14 ip
7fb0cac66ba8 sp 7fff209aa400 error 4 in
libc-2.14.1.so[7fb0cac1e000+187000]
[Tue Apr 7 16:13:02 2015] spamdyke[23130]: segfault at 14 ip
7f47bd14eba8 sp 7fff5b5fd1e0 error 4 in
libc-2.14.1.so[7f47bd106000+187000]
[Tue Apr 7 17:22:50 2015] spamdyke[26691]: segfault at 14 ip
7f24e499bba8 sp 7fff0cbd2060 error 4 in
libc-2.14.1.so[7f24e4953000+187000]
[Tue Apr 7 22:37:46 2015] spamdyke[6768]: segfault at 14 ip
7fcd7c1ffba8 sp 7fff0fd874f0 error 4 in
libc-2.14.1.so[7fcd7c1b7000+187000]
[Tue Apr 7 22:37:48 2015] spamdyke[6775]: seg

Re: [spamdyke-users] Segfault in spamdyke (libc-2.14.1.so) since use of version 5 | *** glibc detected *** /usr/local/bin/spamdyke: double free or corruption (fasttop):

[Sam Clippinger via spamdyke-users]

Wow Gentoo, really?  Every time I consider Gentoo, I start getting flashbacks of installing Slackware 1.2 from floppy disks back in the elder days.  Nevertheless, I tried installing Gentoo to try to duplicate your environment and gave up about halfway through the install guide... I can't remember how far I got, but it was one of the pages in the low 500's, I think. :)Anyway, I've spent the last couple days hunting bugs and I've found a few that might be responsible for these errors.  Could you try applying this patch and see if it resolves the segfaults?  It should apply cleanly to spamdyke 5.0.0:	cd /path/to/src/spamdyke-5.0.0	patch -p1 < spamdyke-5.0.0-segfault.patch	makeThen install the new binary over the old one.If this doesn't fix your crashes, at least it'll fix a lot of other potential ones!

spamdyke-5.0.0-segfault.patch
Description: Binary data

-- Sam Clippinger

On Apr 9, 2015, at 11:05 PM, Konstantin via spamdyke-users  wrote:Hi Everyone!On a virtual gentoo server I currently have:ebuild: dev-libs/openssl-1.0.1l-r1OpenSSL 1.0.1l 15 Jan 2015ebuild: sys-devel/gcc-4.8.4gcc (Gentoo 4.8.4 p1.4, pie-0.6.1) 4.8.4ebuild: sys-libs/glibc-2.20-r2glibc 2.20ebuild: sys-kernel/gentoo-sources-3.17.7custom build kernel 3.17.7-gentoo-domUNot sure about /etc/xinetd.d/smtps_psa since I don't have it but unning process looks like this:10821 ?    S  4:07 /usr/bin/tcpserver -p -v -R -x /etc/tcprules.d/tcp.qmail-smtp.cdb -c 40 -u 201 -g 200 0.0.0.0 smtp spamdyke -f /etc/spamdyke/spamdyke.conf /var/qmail/bin/qmail-smtpd /var/vpopmail/bin/vchkpw /bin/trueLet me know if I can provide you something more relevant, Sam.-- BR,KonstantinOn 2015-04-09 20:27, Sam Clippinger via spamdyke-users wrote:I've been looking through the many log files you sent, thank for beingso thorough! From what I can see in the files you and Konstantin havesent, it looks like the problem lies somewhere in the TLS/SSL cleanuproutine. In your log files, all of the crashes seem to happen justafter a client fails to connect with SMTPS due to a cipher negotiationproblem. There are only four different OpenSSL error codes beinglogged, which translate as: error:1406B0CB:SSL routines:GET_CLIENT_MASTER_KEY:peer error nocipher error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocolversionThose appear to be the only connections that are crashing, otherconnections that successfully negotiate their TLS/SSL sessions seem tobe fine.I haven't had any success in reproducing this bug yet, but I'm stillworking on it. I'm curious about some of the versions on your serverthough -- could you send me the version numbers of OpenSSL, gcc andthe kernel you're running? Could you also send me your/etc/xinetd.d/smtps_psa file (the one that starts spamdyke for SMTPS)?I'd like to see how it's being started so I can try to simulate it.Thanks!-- Sam ClippingerOn Apr 7, 2015, at 5:44 PM, Dirk via spamdyke-users wrote:Dear Sam,at first thank you for glorious work with spamdyke! I'm using itsinceseveral years and it's very helpful to me.At 30th march 2015 I've done an upgrade to version 5 (previous: last4version). Since then I often get a segfault in spamdyke:Tue Apr 7 12:05:19 2015] spamdyke[13607]: segfault at 14 ip7f60ce1e3ba8 sp 7fff6bac3ce0 error 4 inlibc-2.14.1.so[7f60ce19b000+187000][Tue Apr 7 12:16:20 2015] spamdyke[13959]: segfault at 14 ip7fe1145bdba8 sp 7fffa6426b90 error 4 inlibc-2.14.1.so[7fe114575000+187000][Tue Apr 7 12:47:31 2015] spamdyke[15309]: segfault at 14 ip7f9971e49ba8 sp 7fffa03aad20 error 4 inlibc-2.14.1.so[7f9971e01000+187000][Tue Apr 7 15:30:51 2015] spamdyke[21795]: segfault at 14 ip7fb0cac66ba8 sp 7fff209aa400 error 4 inlibc-2.14.1.so[7fb0cac1e000+187000][Tue Apr 7 16:13:02 2015] spamdyke[23130]: segfault at 14 ip7f47bd14eba8 sp 7fff5b5fd1e0 error 4 inlibc-2.14.1.so[7f47bd106000+187000][Tue Apr 7 17:22:50 2015] spamdyke[26691]: segfault at 14 ip7f24e499bba8 sp 7fff0cbd2060 error 4 inlibc-2.14.1.so[7f24e4953000+187000][Tue Apr 7 22:37:46 2015] spamdyke[6768]: segfault at 14 ip7fcd7c1ffba8 sp 7fff0fd874f0 error 4 inlibc-2.14.1.so[7fcd7c1b7000+187000][Tue Apr 7 22:37:48 2015] spamdyke[6775]: segfault at 1a ip7fb2f498eba8 sp 7fff6f12c380 error 4 inlibc-2.14.1.so[7fb2f4946000+187000][Tue Apr 7 22:37:49 2015] spamdyke[6780]: segfault at 1a ip7f4e9ee6fba8 sp 7fff517bbbd0 error 4 inlibc-2.14.1.so[7f4e9ee27000+187000][Tue Apr 7 22:38:11 2015] spamdyke[6764]: segfault at c ip7ffc08375ba8sp 7fff0c363ba0 error 4 in libc-2.14.1.so[7ffc0832d000+187000][Tue Apr 7 23:15:12 2015] spamdyke[10219]: segfault at 14 ip7ff1e6e54ba8 sp 7fffad8b0870 error 4 inlibc-2.14.1.so[7ff1e6e0c000+187000][Tue Apr 7 23:30:42 2015] spamdyke[10658]: segfault at 14 ip7f7e5db7eba8 sp 7fff00aa9eb0 

Re: [spamdyke-users] Segfault in spamdyke (libc-2.14.1.so) since use of version 5 | *** glibc detected *** /usr/local/bin/spamdyke: double free or corruption (fasttop):

[Konstantin via spamdyke-users]

Hi Everyone,


On Apr 7, 2015, at 5:44 PM, Dirk via spamdyke-users
 wrote:


Dear Sam,

at first thank you for glorious work with spamdyke! I'm using it
since
several years and it's very helpful to me.

At 30th march 2015 I've done an upgrade to version 5 (previous: last
4
version). Since then I often get a segfault in spamdyke:

Tue Apr 7 12:05:19 2015] spamdyke[13607]: segfault at 14 ip
7f60ce1e3ba8 sp 7fff6bac3ce0 error 4 in
libc-2.14.1.so[7f60ce19b000+187000]


On 2015-04-07 18:16, Sam Clippinger via spamdyke-users wrote:

If spamdyke was compiled on this server, I doubt the problem is
glibc... it's more likely the messages are showing a location within
glibc because the fault occurs within a library function. From those
log entries, I think the most likely clues are the ones mentioning a
double free or corrupt memory -- that may indicate a bad pointer being
passed to free() somewhere. Definitely a bug!

Is there any chance you could recompile spamdyke with excessive output
and capture a full log of one of these crashes? That would be an
immense help in reproducing this problem. To enable excessive output,
run these commands in the spamdyke source folder:
 ./configure --enable-excessive-output
 make
Then copy the new spamdyke binary over the old one. To capture full
log files, add the "full-log-dir" option to your configuration file.
When a crash happens, the full log file will spamdyke's environment
and configuration, as well as every move it made up until the crash.
Feel free to send it to me privately if you don't want to post it to
the list.

In the meantime, I'll do some more experimentation with the
earlytalker filter and SMTPS, since those two features seem to be
visible in the logs. There's definitely a bug in there somewhere if
it's happening so frequently on your server.

Thanks for reporting this!

-- Sam Clippinger


It seem that I have similar problem with version 5.0.0 against local 
glibc-2.19.

In my log file I can see many crashes like this:

kernel: [5030424.419362] traps: spamdyke[14595] general protection 
ip:7fed7de9f035 sp:78625050 error:0 in 
libc-2.19.so[7fed7de57000+19a000]


I'll recompile spamdyke with excessive output option and send you my 
logs soon, Sam. Thank you.


--
Konstantin
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Re: [spamdyke-users] Segfault in spamdyke (libc-2.14.1.so) since use of version 5 | *** glibc detected *** /usr/local/bin/spamdyke: double free or corruption (fasttop):

[Sam Clippinger via spamdyke-users]

If spamdyke was compiled on this server, I doubt the problem is glibc... it's 
more likely the messages are showing a location within glibc because the fault 
occurs within a library function.  From those log entries, I think the most 
likely clues are the ones mentioning a double free or corrupt memory -- that 
may indicate a bad pointer being passed to free() somewhere.  Definitely a bug!

Is there any chance you could recompile spamdyke with excessive output and 
capture a full log of one of these crashes?  That would be an immense help in 
reproducing this problem.  To enable excessive output, run these commands in 
the spamdyke source folder:
./configure --enable-excessive-output
make
Then copy the new spamdyke binary over the old one.  To capture full log files, 
add the "full-log-dir" option to your configuration file.  When a crash 
happens, the full log file will spamdyke's environment and configuration, as 
well as every move it made up until the crash.  Feel free to send it to me 
privately if you don't want to post it to the list.

In the meantime, I'll do some more experimentation with the earlytalker filter 
and SMTPS, since those two features seem to be visible in the logs.  There's 
definitely a bug in there somewhere if it's happening so frequently on your 
server.

Thanks for reporting this!

-- Sam Clippinger




On Apr 7, 2015, at 5:44 PM, Dirk via spamdyke-users 
 wrote:

> Dear Sam,
> 
> at first thank you for glorious work with spamdyke! I'm using it since
> several years and it's very helpful to me.
> 
> At 30th march 2015 I've done an upgrade to version 5 (previous: last 4
> version). Since then I often get a segfault in spamdyke:
> 
> Tue Apr  7 12:05:19 2015] spamdyke[13607]: segfault at 14 ip
> 7f60ce1e3ba8 sp 7fff6bac3ce0 error 4 in
> libc-2.14.1.so[7f60ce19b000+187000]
> [Tue Apr  7 12:16:20 2015] spamdyke[13959]: segfault at 14 ip
> 7fe1145bdba8 sp 7fffa6426b90 error 4 in
> libc-2.14.1.so[7fe114575000+187000]
> [Tue Apr  7 12:47:31 2015] spamdyke[15309]: segfault at 14 ip
> 7f9971e49ba8 sp 7fffa03aad20 error 4 in
> libc-2.14.1.so[7f9971e01000+187000]
> [Tue Apr  7 15:30:51 2015] spamdyke[21795]: segfault at 14 ip
> 7fb0cac66ba8 sp 7fff209aa400 error 4 in
> libc-2.14.1.so[7fb0cac1e000+187000]
> [Tue Apr  7 16:13:02 2015] spamdyke[23130]: segfault at 14 ip
> 7f47bd14eba8 sp 7fff5b5fd1e0 error 4 in
> libc-2.14.1.so[7f47bd106000+187000]
> [Tue Apr  7 17:22:50 2015] spamdyke[26691]: segfault at 14 ip
> 7f24e499bba8 sp 7fff0cbd2060 error 4 in
> libc-2.14.1.so[7f24e4953000+187000]
> [Tue Apr  7 22:37:46 2015] spamdyke[6768]: segfault at 14 ip
> 7fcd7c1ffba8 sp 7fff0fd874f0 error 4 in
> libc-2.14.1.so[7fcd7c1b7000+187000]
> [Tue Apr  7 22:37:48 2015] spamdyke[6775]: segfault at 1a ip
> 7fb2f498eba8 sp 7fff6f12c380 error 4 in
> libc-2.14.1.so[7fb2f4946000+187000]
> [Tue Apr  7 22:37:49 2015] spamdyke[6780]: segfault at 1a ip
> 7f4e9ee6fba8 sp 7fff517bbbd0 error 4 in
> libc-2.14.1.so[7f4e9ee27000+187000]
> [Tue Apr  7 22:38:11 2015] spamdyke[6764]: segfault at c ip 7ffc08375ba8
> sp 7fff0c363ba0 error 4 in libc-2.14.1.so[7ffc0832d000+187000]
> [Tue Apr  7 23:15:12 2015] spamdyke[10219]: segfault at 14 ip
> 7ff1e6e54ba8 sp 7fffad8b0870 error 4 in
> libc-2.14.1.so[7ff1e6e0c000+187000]
> [Tue Apr  7 23:30:42 2015] spamdyke[10658]: segfault at 14 ip
> 7f7e5db7eba8 sp 7fff00aa9eb0 error 4 in
> libc-2.14.1.so[7f7e5db36000+187000]
> [Wed Apr  8 00:04:28 2015] spamdyke[12967]: segfault at 14 ip
> 7f53171f2ba8 sp 7fff6b2988d0 error 4 in
> libc-2.14.1.so[7f53171aa000+187000]
> [Wed Apr  8 00:04:51 2015] spamdyke[12983]: segfault at 14 ip
> 7f08fecd3ba8 sp 7fff780fdd80 error 4 in
> libc-2.14.1.so[7f08fec8b000+187000]
> [Wed Apr  8 00:18:19 2015] spamdyke[13457]: segfault at 14 ip
> 7fb3059d7ba8 sp 7fffb221b350 error 4 in
> libc-2.14.1.so[7fb30598f000+187000]
> [Wed Apr  8 00:18:31 2015] spamdyke[13463]: segfault at 14 ip
> 7f1a1a635ba8 sp 7fff32b32180 error 4 in
> libc-2.14.1.so[7f1a1a5ed000+187000]
> 
> 
> 
> It's an OpenSuse 12.1 under Plesk with Qmail. In /var/log/maillog you can
> find these entries:
> 
> 
> Apr  7 22:37:45 master /var/qmail/bin/relaylock[6770]:
> /var/qmail/bin/relaylock: mail from 190.24.206.141:65305
> (static-190-24-206-141.static.etb.net.co)
> Apr  7 22:37:47 master /var/qmail/bin/relaylock[6772]:
> /var/qmail/bin/relaylock: mail from 188.138.1.218:40092
> (atlantic381.dedicatedpanel.com)
> Apr  7 22:37:47 master /var/qmail/bin/relaylock[6773]:
> /var/qmail/bin/relaylock: mail from 188.138.1.218:41403
> (atlantic381.dedicatedpanel.com)
> Apr  7 22:37:47 master spamdyke[6773]: FILTER_EARLYTALKER delay: 25
> Apr  7 22:37:48 master /var/qmail/bin/relaylock[6775]:
> /var/qmail/bin/relaylock: mail from 188.138.1.218:41839
> (atlantic381.dedicatedpanel.com)
> Apr  7 22:37:48 master spamdyke[6775]: FILTER_EARLYTALKER delay: 25
> Apr  7 

[spamdyke-users] Segfault in spamdyke (libc-2.14.1.so) since use of version 5 | *** glibc detected *** /usr/local/bin/spamdyke: double free or corruption (fasttop):

[Dirk via spamdyke-users]

Dear Sam,

at first thank you for glorious work with spamdyke! I'm using it since
several years and it's very helpful to me.

At 30th march 2015 I've done an upgrade to version 5 (previous: last 4
version). Since then I often get a segfault in spamdyke:

Tue Apr  7 12:05:19 2015] spamdyke[13607]: segfault at 14 ip
7f60ce1e3ba8 sp 7fff6bac3ce0 error 4 in
libc-2.14.1.so[7f60ce19b000+187000]
[Tue Apr  7 12:16:20 2015] spamdyke[13959]: segfault at 14 ip
7fe1145bdba8 sp 7fffa6426b90 error 4 in
libc-2.14.1.so[7fe114575000+187000]
[Tue Apr  7 12:47:31 2015] spamdyke[15309]: segfault at 14 ip
7f9971e49ba8 sp 7fffa03aad20 error 4 in
libc-2.14.1.so[7f9971e01000+187000]
[Tue Apr  7 15:30:51 2015] spamdyke[21795]: segfault at 14 ip
7fb0cac66ba8 sp 7fff209aa400 error 4 in
libc-2.14.1.so[7fb0cac1e000+187000]
[Tue Apr  7 16:13:02 2015] spamdyke[23130]: segfault at 14 ip
7f47bd14eba8 sp 7fff5b5fd1e0 error 4 in
libc-2.14.1.so[7f47bd106000+187000]
[Tue Apr  7 17:22:50 2015] spamdyke[26691]: segfault at 14 ip
7f24e499bba8 sp 7fff0cbd2060 error 4 in
libc-2.14.1.so[7f24e4953000+187000]
[Tue Apr  7 22:37:46 2015] spamdyke[6768]: segfault at 14 ip
7fcd7c1ffba8 sp 7fff0fd874f0 error 4 in
libc-2.14.1.so[7fcd7c1b7000+187000]
[Tue Apr  7 22:37:48 2015] spamdyke[6775]: segfault at 1a ip
7fb2f498eba8 sp 7fff6f12c380 error 4 in
libc-2.14.1.so[7fb2f4946000+187000]
[Tue Apr  7 22:37:49 2015] spamdyke[6780]: segfault at 1a ip
7f4e9ee6fba8 sp 7fff517bbbd0 error 4 in
libc-2.14.1.so[7f4e9ee27000+187000]
[Tue Apr  7 22:38:11 2015] spamdyke[6764]: segfault at c ip 7ffc08375ba8
sp 7fff0c363ba0 error 4 in libc-2.14.1.so[7ffc0832d000+187000]
[Tue Apr  7 23:15:12 2015] spamdyke[10219]: segfault at 14 ip
7ff1e6e54ba8 sp 7fffad8b0870 error 4 in
libc-2.14.1.so[7ff1e6e0c000+187000]
[Tue Apr  7 23:30:42 2015] spamdyke[10658]: segfault at 14 ip
7f7e5db7eba8 sp 7fff00aa9eb0 error 4 in
libc-2.14.1.so[7f7e5db36000+187000]
[Wed Apr  8 00:04:28 2015] spamdyke[12967]: segfault at 14 ip
7f53171f2ba8 sp 7fff6b2988d0 error 4 in
libc-2.14.1.so[7f53171aa000+187000]
[Wed Apr  8 00:04:51 2015] spamdyke[12983]: segfault at 14 ip
7f08fecd3ba8 sp 7fff780fdd80 error 4 in
libc-2.14.1.so[7f08fec8b000+187000]
[Wed Apr  8 00:18:19 2015] spamdyke[13457]: segfault at 14 ip
7fb3059d7ba8 sp 7fffb221b350 error 4 in
libc-2.14.1.so[7fb30598f000+187000]
[Wed Apr  8 00:18:31 2015] spamdyke[13463]: segfault at 14 ip
7f1a1a635ba8 sp 7fff32b32180 error 4 in
libc-2.14.1.so[7f1a1a5ed000+187000]



It's an OpenSuse 12.1 under Plesk with Qmail. In /var/log/maillog you can
find these entries:


Apr  7 22:37:45 master /var/qmail/bin/relaylock[6770]:
/var/qmail/bin/relaylock: mail from 190.24.206.141:65305
(static-190-24-206-141.static.etb.net.co)
Apr  7 22:37:47 master /var/qmail/bin/relaylock[6772]:
/var/qmail/bin/relaylock: mail from 188.138.1.218:40092
(atlantic381.dedicatedpanel.com)
Apr  7 22:37:47 master /var/qmail/bin/relaylock[6773]:
/var/qmail/bin/relaylock: mail from 188.138.1.218:41403
(atlantic381.dedicatedpanel.com)
Apr  7 22:37:47 master spamdyke[6773]: FILTER_EARLYTALKER delay: 25
Apr  7 22:37:48 master /var/qmail/bin/relaylock[6775]:
/var/qmail/bin/relaylock: mail from 188.138.1.218:41839
(atlantic381.dedicatedpanel.com)
Apr  7 22:37:48 master spamdyke[6775]: FILTER_EARLYTALKER delay: 25
Apr  7 22:37:49 master /var/qmail/bin/relaylock[6778]:
/var/qmail/bin/relaylock: mail from 188.138.1.218:42387
(atlantic381.dedicatedpanel.com)
Apr  7 22:37:49 master spamdyke[6778]: FILTER_EARLYTALKER delay: 25
Apr  7 22:37:49 master /var/qmail/bin/relaylock[6780]:
/var/qmail/bin/relaylock: mail from 188.138.1.218:42409
(atlantic381.dedicatedpanel.com)
Apr  7 22:37:49 master spamdyke[6780]: FILTER_EARLYTALKER delay: 25
Apr  7 22:37:49 master spamdyke[6778]: ERROR: unable to start SSL/TLS
connection: A protocol or library failure occurred,
error:1406B0CB:lib(20):func(107):reason(203)
Apr  7 22:37:49 master spamdyke[6778]: ERROR: unable to start SMTPS due to a
protocol failure; closing connection
Apr  7 22:37:49 master /var/qmail/bin/relaylock[6782]:
/var/qmail/bin/relaylock: mail from 188.138.1.218:42898
(atlantic381.dedicatedpanel.com)
Apr  7 22:37:49 master spamdyke[6782]: FILTER_EARLYTALKER delay: 25
Apr  7 22:37:50 master spamdyke[6782]: ERROR: unable to start SSL/TLS
connection: A protocol or library failure occurred,
error:1409442E:lib(20):func(148):reason(1070)
Apr  7 22:37:50 master spamdyke[6782]: ERROR: unable to start SMTPS due to a
protocol failure; closing connection
Apr  7 22:37:50 master spamdyke[6782]: *** glibc detected ***
/usr/local/bin/spamdyke: double free or corruption (fasttop):
0x00651ed0 ***
Apr  7 22:37:51 master spamdyke[6773]: ERROR(The operation failed due to an
I/O error, Connection reset by peer()@(null):1): unable to read from SSL/TLS
stream: .
Apr  7 22:37:51 master spamdyke[6773]: *** glibc detected ***
/usr/local/bin/spamdy