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):
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 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 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
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):
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 spamdyke-users@spamdyke.org 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-usersspamdyke-users@spamdyke.org 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 error 4
