These are probably obvious, but turn up logging to level 5 and see if dbmail-imapd prints anything. I believe there's a way to have postgres log queries that are being run too, but I don't remember how. If neither of those provide any hints, you'd probably have to run a debugger to trace the process. Also, you might record the imap traffic going over the wire... there's an off chance you could be getting hit by some as-yet previously unknown bug in the imap protocol handler or something (but probably look at that as more of a last resort).
---- Original Message ---- From: Richard Barrington <dbmail@dbmail.org> To: DBMail mailinglist <dbmail@dbmail.org> Subject: Re: [Dbmail] Dbmail-imap tacking cpu Sent: Wed, 21 Jul 2004 10:08:54 +1200 > Right then, I came in this morning and it's back. The CPU is pegged > again despite no IMAP client activity. Any suggestions for tracking down > what's going on? > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 14286 dbmail 10 0 1460 1460 1236 S 50.7 0.1 38:50.21 dbmail-imapd > 28547 postgres 15 0 5940 5940 4988 R 30.5 0.6 32:39.53 postmaster > > Rich. > > On Tue, 2004-07-20 at 17:04, Richard Barrington wrote: > > I figured the problem would be a relative rarity. I've been watching for > > it this afternoon after restarting dbmail-imapd, but it hasn't come back > > yet. That's a little confusing, because it was back within an hour the > > previous time. To be fair, we haven't had much email action, so I'll > > give it another couple of days... > > > > Rich. > > > _______________________________________________ > Dbmail mailing list > Dbmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- End Original Message -- -- Jesse Norell [EMAIL PROTECTED] is not my email address; change "administrator" to my first name. --
