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!

Attachment: spamdyke-5.0.0-segfault.patch
Description: Binary data



-- Sam Clippinger




On Apr 9, 2015, at 11:05 PM, Konstantin via spamdyke-users <spamdyke-users@spamdyke.org> 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
<spamdyke-users@spamdyke.org> 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
00007f60ce1e3ba8 sp 00007fff6bac3ce0 error 4 in
libc-2.14.1.so[7f60ce19b000+187000]
[Tue Apr 7 12:16:20 2015] spamdyke[13959]: segfault at 14 ip
00007fe1145bdba8 sp 00007fffa6426b90 error 4 in
libc-2.14.1.so[7fe114575000+187000]
[Tue Apr 7 12:47:31 2015] spamdyke[15309]: segfault at 14 ip
00007f9971e49ba8 sp 00007fffa03aad20 error 4 in
libc-2.14.1.so[7f9971e01000+187000]
[Tue Apr 7 15:30:51 2015] spamdyke[21795]: segfault at 14 ip
00007fb0cac66ba8 sp 00007fff209aa400 error 4 in
libc-2.14.1.so[7fb0cac1e000+187000]
[Tue Apr 7 16:13:02 2015] spamdyke[23130]: segfault at 14 ip
00007f47bd14eba8 sp 00007fff5b5fd1e0 error 4 in
libc-2.14.1.so[7f47bd106000+187000]
[Tue Apr 7 17:22:50 2015] spamdyke[26691]: segfault at 14 ip
00007f24e499bba8 sp 00007fff0cbd2060 error 4 in
libc-2.14.1.so[7f24e4953000+187000]
[Tue Apr 7 22:37:46 2015] spamdyke[6768]: segfault at 14 ip
00007fcd7c1ffba8 sp 00007fff0fd874f0 error 4 in
libc-2.14.1.so[7fcd7c1b7000+187000]
[Tue Apr 7 22:37:48 2015] spamdyke[6775]: segfault at 1a ip
00007fb2f498eba8 sp 00007fff6f12c380 error 4 in
libc-2.14.1.so[7fb2f4946000+187000]
[Tue Apr 7 22:37:49 2015] spamdyke[6780]: segfault at 1a ip
00007f4e9ee6fba8 sp 00007fff517bbbd0 error 4 in
libc-2.14.1.so[7f4e9ee27000+187000]
[Tue Apr 7 22:38:11 2015] spamdyke[6764]: segfault at c ip
00007ffc08375ba8
sp 00007fff0c363ba0 error 4 in libc-2.14.1.so[7ffc0832d000+187000]
[Tue Apr 7 23:15:12 2015] spamdyke[10219]: segfault at 14 ip
00007ff1e6e54ba8 sp 00007fffad8b0870 error 4 in
libc-2.14.1.so[7ff1e6e0c000+187000]
[Tue Apr 7 23:30:42 2015] spamdyke[10658]: segfault at 14 ip
00007f7e5db7eba8 sp 00007fff00aa9eb0 error 4 in
libc-2.14.1.so[7f7e5db36000+187000]
[Wed Apr 8 00:04:28 2015] spamdyke[12967]: segfault at 14 ip
00007f53171f2ba8 sp 00007fff6b2988d0 error 4 in
libc-2.14.1.so[7f53171aa000+187000]
[Wed Apr 8 00:04:51 2015] spamdyke[12983]: segfault at 14 ip
00007f08fecd3ba8 sp 00007fff780fdd80 error 4 in
libc-2.14.1.so[7f08fec8b000+187000]
[Wed Apr 8 00:18:19 2015] spamdyke[13457]: segfault at 14 ip
00007fb3059d7ba8 sp 00007fffb221b350 error 4 in
libc-2.14.1.so[7fb30598f000+187000]
[Wed Apr 8 00:18:31 2015] spamdyke[13463]: segfault at 14 ip
00007f1a1a635ba8 sp 00007fff32b32180 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 [1])
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 [2])
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 [2])
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 [2])
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 [2])
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 [2])
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 [2])
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):
0x0000000000651ed0 ***
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/spamdyke: double free or corruption (fasttop):
0x0000000000651ed0 ***
Apr 7 22:37:56 master /var/qmail/bin/relaylock[6789]:
/var/qmail/bin/relaylock: mail from 188.138.1.218:43026
(atlantic381.dedicatedpanel.com [2])
Apr 7 22:37:56 master spamdyke[6789]: FILTER_EARLYTALKER delay: 25
Apr 7 22:37:56 master /var/qmail/bin/relaylock[6791]:
/var/qmail/bin/relaylock: mail from 188.138.1.218:55694
(atlantic381.dedicatedpanel.com [2])
Apr 7 22:37:56 master spamdyke[6791]: FILTER_EARLYTALKER delay: 25
Apr 7 22:37:56 master spamdyke[6791]: ERROR: unable to start SSL/TLS
connection: A protocol or library failure occurred,
error:1408A0C1:lib(20):func(138):reason(193)
Apr 7 22:37:56 master spamdyke[6791]: ERROR: unable to start SMTPS
due to a
protocol failure; closing connection
Apr 7 22:37:57 master spamdyke[6789]: 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:57 master spamdyke[6789]: ERROR: unable to start SMTPS
due to a
protocol failure; closing connection
Apr 7 22:37:57 master spamdyke[6789]: *** glibc detected ***
/usr/local/bin/spamdyke: double free or corruption (fasttop):
0x0000000000651ed0 ***
Apr 7 22:38:04 master spamdyke[6549]: TIMEOUT from: (unknown) to:
(unknown)
origin_ip: 95.219.93.25 origin_rdns: (unknown) auth: (unknown)
encryption:
(none) reason: TIMEOUT
It seems to be related to the glibc which is installed on the
machine in
version 2.14.1. Do you have any ideas to solve the problem?
Dirk Kannapinn
CEO | IT-Management
DK ONE TECH
Professional IT-Services
Nauener Stra├če 64, D-13581 Berlin
Fon: +49.180.16666.266.117
Fon: +49.30.351.393.03
Fax: +49.30.351.393.05
SIP: 4918016666266...@sipgate.de
E-Mail: dirk.kannap...@dk-one.de
Web: www.dk-one.de [3]
Inhabergef├╝hrtes Dienstleistungsunternehmen
Inhaber Dirk Kannapinn
USt-ID DE193561612
Der Inhalt dieser E-Mail ist vertraulich und ausschliesslich fuer
den
bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene
Adressat
dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie
bitte,
dass jede Form der Kenntnisnahme, Veroeffentlichung,
Vervielfaeltigung oder
Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten
Sie, sich
in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen.
Contents of this E-Mail are confidentially and exclusively intended
for the
defined addressee. If you should not be the addressee intended of
this
E-Mail or its representatives, then you note please that each form
of the
information, publication, duplication or passing on of contents of
this
E-Mail is illegal. We ask you to set itself in this case with the
sender of
the E-Mail in connection

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

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

Reply via email to