| To: | "'Alex Kirk'" <alex.kirk@sourcefire.com>, <qmail@list.cr.yp.to> |
|---|---|
| Subject: | RE: Dozens of qmail-smtpd processes eating 100% of CPU |
| From: | "Seth Kurtzberg" <seth@cql.com> |
| Date: | Fri, 18 May 2007 13:54:42 -0400 |
| Delivered-to: | sp-com-lists@consult.net |
| Delivered-to: | gmail-qmail@securepoint.com |
| Delivered-to: | sp.com.list@gmail.com |
| Delivered-to: | mailing list qmail@list.cr.yp.to |
| In-reply-to: | <464DE3E0.8070200@sourcefire.com> |
| Mailing-list: | contact qmail-help@list.cr.yp.to; run by ezmlm |
| References: | <464DBC1B.30204@sourcefire.com> <20070518163703.GH29250@marvin.we-be-smart.org> <464DE3E0.8070200@sourcefire.com> |
| Thread-index: | AceZd7dfoBGENK4PSbuy59Nxy+BbIAAAlx+w |
Indeed, it may not be the cause of this particular problem. I did see a similar problem some time ago caused by a truncated message in a queue. Even if it turns out to be irrelevant, it's a good idea not to strand messages in the queue forever. Meanwhile, I've used qmHandle (http://sourceforge.net/projects/qmhandle) to go clean my local and remote queues, which did have a bunch of old messages in them (some without subjects/ or To/From addresess, others with characters that didn't display properly in my terminal), at the urging of Seth Kurtzberg (who appears to have posted off-list, but thanks anyway). I'm not sure that that's even related, but I figure it doesn't hurt. Alex Kirk |
| Previous by Date: | Re: Dozens of qmail-smtpd processes eating 100% of CPU, Alex Kirk |
|---|---|
| Next by Date: | Re: Dozens of qmail-smtpd processes eating 100% of CPU, Kyle Wheeler |
| Previous by Thread: | Re: Dozens of qmail-smtpd processes eating 100% of CPU, Alex Kirk |
| Next by Thread: | Re: Dozens of qmail-smtpd processes eating 100% of CPU, Kyle Wheeler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |