Children keep hanging
I deployed qpsmtpd a few weeks ago, and since that I've been having some trouble. I keep getting stale connections, that show up like this. smtpd13327 0.3 1.6 10032 7932 ?S13:28 0:01 | | \_ ./qpsmtpd [61.0.190.162 : 61.0.190.162 : 13:28:12 2006-10-10] if I strace it, it just hangs on this: strace -p 13327 Process 13327 attached - interrupt to quit read(0, now I've never been able to get the strace from before it hangs unfortunatly, and I will keep trying that, was just wondering if anyone else have seen it, and if you got anywhere with it. andreas
Re: Heads up for users of spamhaus
Last I had read it wasn't an order. It was something the spammers lawyer proposed. The judge has to sign it, and hasn't yet. http://www.spamhaus.org/legal/answer.lasso?ref=3 http://legal-dictionary.thefreedictionary.com/default+judgement ANYWAY - further discussion of the legal aspects of this are off topic for this list, please take them elsewhere. -R At Fri, 06 Oct 2006 16:18:01 -0700, Waitman Gobble wrote: The order was to ICANN regarding the domain name. It is a curious situation though. Waitman James Turnbull wrote: Matt Sergeant wrote: http://wordtothewise.com/Spamhaus_ICANN_order.html If you're using sbl-xbl, consider temporarily switching to cbl until this blows over. The order is essentially meaningless though isn't it? The associated judgement is unenforceable because Spamhaus isn't under the jurisdiction of US law - it's a UK entity. If Linhardt wants to stop them he is going to have to file the same case in a UK court and the laws regarding spam in the UK are considerably different. Regards James Turnbull
Re: Children keep hanging
Try launching qpsmtpd via strace so you can see the entire log, including what comes before that read() call. Warning: that will be VERY verbose - if you are running via tcpserver without forkserver, you can probably just log to /tmp/log.$$ or so you can isolate the flow from the offending process and nuke any old files before your filesystem fills up. Cheers, Brian On Oct 10, 2006, at 7:38 AM, Andreas Marienborg wrote: I deployed qpsmtpd a few weeks ago, and since that I've been having some trouble. I keep getting stale connections, that show up like this. smtpd13327 0.3 1.6 10032 7932 ?S13:28 0:01 | | \_ ./qpsmtpd [61.0.190.162 : 61.0.190.162 : 13:28:12 2006-10-10] if I strace it, it just hangs on this: strace -p 13327 Process 13327 attached - interrupt to quit read(0, now I've never been able to get the strace from before it hangs unfortunatly, and I will keep trying that, was just wondering if anyone else have seen it, and if you got anywhere with it. andreas --- Brian Szymanski [EMAIL PROTECTED]
Re: Children keep hanging
On 2006-10-10 22:11:21 +0200, Andreas Marienborg wrote: alarm(1200) = 0 ^^^ That should kill the process after 20 minutes. Doesn't it? read(0, -- _ | Peter J. Holzer| Schlagfertigkeit ist das, was einem |_|_) | Sysadmin WSR | auf dem Nachhauseweg einfällt. | | | [EMAIL PROTECTED] |-- Lars 'Cebewee' Noschinski in dasr. __/ | http://www.hjp.at/ | signature.asc Description: Digital signature
Re: Children keep hanging
Indeed it did. I could have sworn I had seen processes hanging around much longer than that though, but that might have been a different symptom all together. Is there any reason to have a 20 minutes timeout? Can it be shorter? andreas On 10. okt. 2006, at 22.52, Peter J. Holzer wrote: On 2006-10-10 22:11:21 +0200, Andreas Marienborg wrote: alarm(1200) = 0 ^^^ That should kill the process after 20 minutes. Doesn't it? read(0, -- _ | Peter J. Holzer| Schlagfertigkeit ist das, was einem |_|_) | Sysadmin WSR | auf dem Nachhauseweg einfällt. | | | [EMAIL PROTECTED] |-- Lars 'Cebewee' Noschinski in dasr. __/ | http://www.hjp.at/ |
Re: Children keep hanging
Andreas Marienborg wrote: Indeed it did. I could have sworn I had seen processes hanging around much longer than that though, but that might have been a different symptom all together. Is there any reason to have a 20 minutes timeout? Yes. Stupid users who insist on sending 80MB files over a slow link. What's worse is that qpsmtpd may eventually accept the file, but the remote server can timeout between end of data and '220 Queued'. This will lead to the same message being retried 1 hour, 2 hours, 4 hours, 8 hours, etc, until it expires from the remote queue. Trust me, someone had a serious talking to after *that* incident... John
