I've also tried editing /etc/spamdyke.conf
Added a line full-log-dir=/root/smtp_full_log/ also set log-level=excessive The latter has made the mail log to output a lot more information than before but I'm not sure if which part would be useful. (I've reverted this for now.) Also there is still nothing in /root/smtp_full_log/ Kind regards, Koha From: [email protected] [mailto:[email protected]] On Behalf Of Emailitis Sent: 30 October 2012 16:16 To: 'spamdyke users' Subject: Re: [spamdyke-users] Spamdyke CPU usage Thanks Sam for the response, Our plesk server runs CentOS 5.8, Spamdyke 4.2.0 Mailman version 2.1.9 I have recompiled spamdyke --with-excessive-output. Ran make and copied spamdyke to /usr/bin/ Changed my config file service smtp { socket_type = stream protocol = tcp wait = no disable = no user = root flags = IPv6 instances = UNLIMITED env = SMTPAUTH=1 server = /var/qmail/bin/tcp-env server_args = -Rt0 /var/qmail/bin/relaylock /usr/local/bin/spamdyke -f /etc/spamdyke.conf -L /root/smtp_full_log/ /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true } And restarted qmail, xinetd and courier-imap. I don't see anything different nor do can I see anything in /root/smtp_full_log. Is there something I missed out? Kind regards, Koha -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sam Clippinger Sent: 30 October 2012 14:38 To: spamdyke users Subject: Re: [spamdyke-users] Spamdyke CPU usage There's no incompatibility that I'm aware of; this mailing list is hosted by mailman and filtered by spamdyke with no problems. A few questions: Is the mailman process running on the same server as spamdyke, or a different one? What OS and version are you running? What versions of spamdyke and mailman? Since you seem to be able to trigger this bug relatively easily, it would be extremely helpful if you could recompile spamdyke with excessive output (run "./configure --with-excessive-output ; make"), then enable full logging ("full-log-dir" option). The log from one of these "stuck" processes should show exactly what spamdyke is doing when the bug occurs and would probably contain all the info I'd need to reproduce it and fix it. It'll contain real domain names and such, so you'll probably want to send it to me privately. As soon as I can figure out how to trigger this myself, I should be able to fix it very quickly. -- Sam Clippinger On Oct 30, 2012, at 9:14 AM, Koha wrote: > After turning spamdyke back on, this problem came back... > > The spamdyke CPU > An email sent to a mailing list went through to some but not all recipients. > > So I did: > Disable spamdyke (editing /etc/xinetd.d/smtp_psa), Restart qmail, > xinetd, courier-imap Killall -9 spamdyke (The CPU was high, but > dropped after killing it) Restart mailman > > As soon as I restarted mailman, the email was sent to the remaining > recipients. > > It's not ideal to switch off spamdyke and restart mailman every time > the mailing list gets stuck, as it would allow spam in the short time > while spamdyke is disabled and we also don't know when the mailing > list would get stuck. > > Is anyone aware of this kind of problem? Is there some kind of > compatibility issue between spamdyke and mailman? > > Kind regards, > > Koha Choji > > -----Original Message----- > From: <mailto:[email protected]> [email protected] > [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of Emailitis > Sent: 30 October 2012 13:07 > To: 'spamdyke users' > Subject: Re: [spamdyke-users] Spamdyke CPU usage > > By removing the spamdyke entry on /etc/xinetd.d/smtp_psa I've disabled > spamdyke temporarily. > > This seems to have let all the emails that were held up to come through. > > Koha > > -----Original Message----- > From: <mailto:[email protected]> [email protected] > [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of Koha > Sent: 30 October 2012 10:23 > To: 'spamdyke users' > Subject: Re: [spamdyke-users] Spamdyke CPU usage > > Right, this one seems to be quite a tricky problem... > > It turns out emails as a part of mailing lists that are managed on our > server by Mailman has been held up - weren't getting through. > > When we "kill" spamdyke, we see on the mail log that spamdyke is > ALLOWing these emails. However, qmail wasn't starting the mail delivery. > Another spamdyke process takes its place. > > Every time we run "killall -9 spamdyke" we get about 9 entries of this > spamdyke ALLOWing emails, and they all show up to be the same ones! > > Eventually, after killing all the spamdyke processes and the CPU usage > goes down, but the emails are still held up. > > When we restart mailman, spamdyke CPU usage goes up again. > > Does anyone have any ideas what is going on? > > Kind regards, > > > Koha Choji > > > > > > > -----Original Message----- > From: <mailto:[email protected]> [email protected] > [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of Sebastian > Grewe > Sent: 25 October 2012 17:16 > To: spamdyke users > Subject: Re: [spamdyke-users] Spamdyke CPU usage > > Probably really stuck then and not doing much anymore :-( > > Sorry to not be of further help but maybe Sam has some ideas still :-) > > Cheers, > Sebastian > > On 25.10.2012, at 18:11, "Emailitis" < <mailto:[email protected]> [email protected]> wrote: > >> Sorry Sebastian, I didn't notice your response! >> >> I just ran >> Strace -f -p 18211 >> But I get the same results as before...am I doing it right? >> >> Koha Choji >> >> -----Original Message----- >> From: <mailto:[email protected]> [email protected] >> [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of Emailitis >> Sent: 25 October 2012 17:01 >> To: 'spamdyke users' >> Subject: Re: [spamdyke-users] Spamdyke CPU usage >> >> The only spamdyke process to appear when I run top is that particular >> process. No other process seems to be using that much CPU power. >> >> Log messages... something like this? >> [root@our_plesk_server ~]# cat /var/log/messages | grep spamdyke Oct >> 25 >> 11:10:51 our_plesk_server kernel: grsec: From XX.XX.XX.XX: process >> /usr/local/bin/spamdyke(spamdyke:18211) attached to via ptrace by >> /usr/bin/strace[strace:31611] uid/euid:0/0 gid/egid:0/0, parent >> /bin/bash[bash:25024] uid/euid:0/0 gid/egid:0/0 Oct 25 13:03:16 >> our_plesk_server kernel: grsec: From XX.XX.XX.XX: process >> /usr/local/bin/spamdyke(spamdyke:18211) attached to via ptrace by >> /usr/bin/strace[strace:15386] uid/euid:0/0 gid/egid:0/0, parent >> /bin/bash[bash:25024] uid/euid:0/0 gid/egid:0/0 >> >> This log starts from Oct 21 06:52:10. >> >> I'm a bit unsure about killing it but so far we haven't had any >> trouble with running things on our server. Could this be a false reading? >> >> Kind regards, >> >> Koha Choji >> >> >> -----Original Message----- >> From: <mailto:[email protected]> [email protected] >> [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of Sam >> Clippinger >> Sent: 25 October 2012 16:46 >> To: spamdyke users >> Subject: Re: [spamdyke-users] Spamdyke CPU usage >> >> Also, stopping qmail won't stop any running spamdyke or qmail-smtpd >> processes, it'll only stop new ones from being created. >> >> Are you seeing high CPU usage from all spamdyke processes or just a >> single one? Are you seeing any log messages from this/these high CPU > process/es? >> It'd be great to see what it's doing with strace but I'm also curious >> if another spamdyke process will use high CPU if the existing one is > killed. >> >> -- Sam Clippinger >> >> >> >> >> On Oct 25, 2012, at 10:27 AM, Sebastian Grewe wrote: >> >>> Hey, >>> >>> Try strace -f to follow any child's created? Maybe there is more to see. >>> >>> Cheers, >>> Sebastian >>> >>> On 25.10.2012, at 15:54, "J. Kendzorra" < <mailto:[email protected]> [email protected]> wrote: >>> >>>> Am 25.10.2012 14:06, schrieb Emailitis: >>>>> Thanks, J for the response! >>>>> >>>>> Runing strace doesn't seem to give me much, I hit ctrl+c after a >>>>> minute or so. >>>>> >>>>> [root@our_plesk_server ~]# strace 18211 >>>>> Strace: 18211 attached - interrupt to quit Process 18211 detached >>>>> [root@our_plesk_server ~]# >>>> >>>> Doesn't appear to be Spamdyke then ... you sure about that? >>>> >>>> J. >>>> >>>> _______________________________________________ >>>> spamdyke-users mailing list >>>> <mailto:[email protected]> [email protected] >>>> <http://www.spamdyke.org/mailman/listinfo/spamdyke-users> http://www.spamdyke.org/mailman/listinfo/spamdyke-users >>> _______________________________________________ >>> spamdyke-users mailing list >>> <mailto:[email protected]> [email protected] >>> <http://www.spamdyke.org/mailman/listinfo/spamdyke-users> http://www.spamdyke.org/mailman/listinfo/spamdyke-users >> >> _______________________________________________ >> spamdyke-users mailing list >> <mailto:[email protected]> [email protected] >> <http://www.spamdyke.org/mailman/listinfo/spamdyke-users> http://www.spamdyke.org/mailman/listinfo/spamdyke-users >> >> _______________________________________________ >> spamdyke-users mailing list >> <mailto:[email protected]> [email protected] >> <http://www.spamdyke.org/mailman/listinfo/spamdyke-users> http://www.spamdyke.org/mailman/listinfo/spamdyke-users >> >> _______________________________________________ >> spamdyke-users mailing list >> <mailto:[email protected]> [email protected] >> <http://www.spamdyke.org/mailman/listinfo/spamdyke-users> http://www.spamdyke.org/mailman/listinfo/spamdyke-users > _______________________________________________ > spamdyke-users mailing list > <mailto:[email protected]> [email protected] > <http://www.spamdyke.org/mailman/listinfo/spamdyke-users> http://www.spamdyke.org/mailman/listinfo/spamdyke-users > > _______________________________________________ > spamdyke-users mailing list > <mailto:[email protected]> [email protected] > <http://www.spamdyke.org/mailman/listinfo/spamdyke-users> http://www.spamdyke.org/mailman/listinfo/spamdyke-users > > _______________________________________________ > spamdyke-users mailing list > <mailto:[email protected]> [email protected] > <http://www.spamdyke.org/mailman/listinfo/spamdyke-users> http://www.spamdyke.org/mailman/listinfo/spamdyke-users > > _______________________________________________ > spamdyke-users mailing list > <mailto:[email protected]> [email protected] > <http://www.spamdyke.org/mailman/listinfo/spamdyke-users> http://www.spamdyke.org/mailman/listinfo/spamdyke-users _______________________________________________ spamdyke-users mailing list <mailto:[email protected]> [email protected] <http://www.spamdyke.org/mailman/listinfo/spamdyke-users> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
_______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
