Re: [spamdyke-users] Segfault with Spamdyke 4.1.0
Last night, David Stiller kindly allowed me to access his server and run some tests, with good results. I found at least one bug in spamdyke that causes segfaults. If any of the options dns-blacklist-file, dns-whitelist-file, rhs-blacklist-file or rhs-whitelist-file are used and the given file is empty (or contains only comments/whitespace), spamdyke will crash. I'll try to create a new version this weekend to fix this bug (and a couple of others). However, since you're using the config-dir option, is it possible that a configuration folder contains one of those options referencing an empty file? Or are your segfaults being caused by something else? -- Sam Clippinger On 10/24/10 9:41 PM, Ken S. wrote: On Thu, Oct 21, 2010 at 3:36 PM, Sam Clippingers...@silence.org wrote: 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 Sam: I've just switched my logging level back to info and enable the 'full-log-dir' option to start dumping to a directory. I was going to recompile with the excessive option but when I looked at the output of one of the files in the directory I saw data sizes logged. Looks like this: 10/24/2010 22:29:26 FROM CHILD, FILTERED: 14 bytes 250-STARTTLS 10/24/2010 22:29:26 FROM CHILD TO REMOTE: 16 bytes 250-PIPELINING 10/24/2010 22:29:26 FROM CHILD TO REMOTE: 14 bytes 250-8BITMIME 10/24/2010 22:29:26 FROM CHILD TO REMOTE: 19 bytes 250-SIZE 2500 Spamdyke hasn't segfaulted since 22:40 EST last Thursday: Oct 21 22:40:43 mail kernel: spamdyke[2940]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 I'll keep watching the logs and if it faults again I'll check the files in the full-log-dir and post to this thread. Thx! -ken 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 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 12:48:29 mail kernel: spamdyke[24247]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 13:32:40 rsmail kernel: spamdyke[5630]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 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 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
Re: [spamdyke-users] Segfault with Spamdyke 4.1.0
Ok, so it's another reason. I've let spamdyke run overnight and i now i have 97 Segfaults again. I think it's more than my config-dir, thats just a workarounf for the mail-sending problem. So sending mail works, but stillt some spammers get disconnected. :-D Sam just send me your IP to access my server. -- Dave Am 25.10.2010 um 04:41 schrieb Ken S.: On Thu, Oct 21, 2010 at 3:36 PM, Sam Clippinger s...@silence.org wrote: 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 Sam: I've just switched my logging level back to info and enable the 'full-log-dir' option to start dumping to a directory. I was going to recompile with the excessive option but when I looked at the output of one of the files in the directory I saw data sizes logged. Looks like this: 10/24/2010 22:29:26 FROM CHILD, FILTERED: 14 bytes 250-STARTTLS 10/24/2010 22:29:26 FROM CHILD TO REMOTE: 16 bytes 250-PIPELINING 10/24/2010 22:29:26 FROM CHILD TO REMOTE: 14 bytes 250-8BITMIME 10/24/2010 22:29:26 FROM CHILD TO REMOTE: 19 bytes 250-SIZE 2500 Spamdyke hasn't segfaulted since 22:40 EST last Thursday: Oct 21 22:40:43 mail kernel: spamdyke[2940]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 I'll keep watching the logs and if it faults again I'll check the files in the full-log-dir and post to this thread. Thx! -ken 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 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 12:48:29 mail kernel: spamdyke[24247]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 13:32:40 rsmail kernel: spamdyke[5630]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 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 spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users -- Have a nice day ... unless you've made other plans. ___ 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
Re: [spamdyke-users] Segfault with Spamdyke 4.1.0
It's more than i thought: [r...@plesk-mail 11:12:33:~] # grep segf /var/log/messages | grep Oct 25 | wc -l 6768 # dmesg | wc -l 2655 I think it got so high as there's someone sending a newsletter. Am 25.10.2010 um 09:38 schrieb David Stiller: Ok, so it's another reason. I've let spamdyke run overnight and i now i have 97 Segfaults again. I think it's more than my config-dir, thats just a workarounf for the mail-sending problem. So sending mail works, but stillt some spammers get disconnected. :-D Sam just send me your IP to access my server. -- Dave Am 25.10.2010 um 04:41 schrieb Ken S.: On Thu, Oct 21, 2010 at 3:36 PM, Sam Clippinger s...@silence.org wrote: 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 Sam: I've just switched my logging level back to info and enable the 'full-log-dir' option to start dumping to a directory. I was going to recompile with the excessive option but when I looked at the output of one of the files in the directory I saw data sizes logged. Looks like this: 10/24/2010 22:29:26 FROM CHILD, FILTERED: 14 bytes 250-STARTTLS 10/24/2010 22:29:26 FROM CHILD TO REMOTE: 16 bytes 250-PIPELINING 10/24/2010 22:29:26 FROM CHILD TO REMOTE: 14 bytes 250-8BITMIME 10/24/2010 22:29:26 FROM CHILD TO REMOTE: 19 bytes 250-SIZE 2500 Spamdyke hasn't segfaulted since 22:40 EST last Thursday: Oct 21 22:40:43 mail kernel: spamdyke[2940]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 I'll keep watching the logs and if it faults again I'll check the files in the full-log-dir and post to this thread. Thx! -ken 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 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 12:48:29 mail kernel: spamdyke[24247]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 13:32:40 rsmail kernel: spamdyke[5630]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 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 spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users -- Have a nice day ... unless you've made other plans. ___ 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 ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Segfault with Spamdyke 4.1.0
Hi Sam! I always get a segmentation fault, when someone ist trying to send a mail with clear text passwords. So sending mail is impossible. If it helps you out, you can access my machine again and do some researches. Full logging doesn't dump anything in these cases, the segf seems to occur before that. It's still Plesk 8.6. 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 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 12:48:29 mail kernel: spamdyke[24247]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 13:32:40 rsmail kernel: spamdyke[5630]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 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 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
Re: [spamdyke-users] Segfault with Spamdyke 4.1.0
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 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 12:48:29 mail kernel: spamdyke[24247]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 13:32:40 rsmail kernel: spamdyke[5630]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 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 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
Re: [spamdyke-users] Segfault with Spamdyke 4.1.0
On Sun, Oct 24, 2010 at 6:12 PM, David Stiller david.stil...@blackbit.de wrote: 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? Sadly, it is not my case. I don't use the 'config-dir' option in my spamdyke.conf file. -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 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 12:48:29 mail kernel: spamdyke[24247]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 13:32:40 rsmail kernel: spamdyke[5630]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 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 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 -- Have a nice day ... unless you've made other plans. ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Segfault with Spamdyke 4.1.0
On Thu, Oct 21, 2010 at 3:36 PM, Sam Clippinger s...@silence.org wrote: 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 Sam: I've just switched my logging level back to info and enable the 'full-log-dir' option to start dumping to a directory. I was going to recompile with the excessive option but when I looked at the output of one of the files in the directory I saw data sizes logged. Looks like this: 10/24/2010 22:29:26 FROM CHILD, FILTERED: 14 bytes 250-STARTTLS 10/24/2010 22:29:26 FROM CHILD TO REMOTE: 16 bytes 250-PIPELINING 10/24/2010 22:29:26 FROM CHILD TO REMOTE: 14 bytes 250-8BITMIME 10/24/2010 22:29:26 FROM CHILD TO REMOTE: 19 bytes 250-SIZE 2500 Spamdyke hasn't segfaulted since 22:40 EST last Thursday: Oct 21 22:40:43 mail kernel: spamdyke[2940]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 I'll keep watching the logs and if it faults again I'll check the files in the full-log-dir and post to this thread. Thx! -ken 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 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 12:48:29 mail kernel: spamdyke[24247]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 13:32:40 rsmail kernel: spamdyke[5630]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 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 spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users -- Have a nice day ... unless you've made other plans. ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
[spamdyke-users] Segfault with Spamdyke 4.1.0
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 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 12:48:29 mail kernel: spamdyke[24247]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 13:32:40 rsmail kernel: spamdyke[5630]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 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 -- Have a nice day ... unless you've made other plans. ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Segfault with Spamdyke 4.1.0
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 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 12:48:29 mail kernel: spamdyke[24247]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 error 4 Oct 21 13:32:40 rsmail kernel: spamdyke[5630]: segfault at 007fbffbfff8 rip 003da6e73013 rsp 007fbffe75a8 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 spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
