The following issue has been RESOLVED. ====================================================================== http://www.dbmail.org/mantis/view.php?id=430 ====================================================================== Reported By: bjohnson Assigned To: aaron ====================================================================== Project: DBMail Issue ID: 430 Category: IMAP daemon Reproducibility: random Severity: major Priority: normal Status: resolved target: Resolution: no change required Fixed in Version: ====================================================================== Date Submitted: 30-Oct-06 18:04 CET Last Modified: 02-Nov-06 02:59 CET ====================================================================== Summary: dbmail-imapd occasionally creates zombies Description: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND nobody 26519 0.0 0.0 0 0 ? Z 04:13 0:00 [dbmail-imapd] <defunct> root 17633 0.0 0.0 3776 656 pts/0 R+ 11:01 0:00 grep Z
I'm not quite sure how to debug this. When dbmail-imapd is in this state, new connections take upwards of a minute before they get a response from the imap server. Stopping dbmail-imapd and restarting kills the zombie and everything goes back to normal. ====================================================================== ---------------------------------------------------------------------- bjohnson - 01-Nov-06 21:48 ---------------------------------------------------------------------- Interesting. I have another server running 2.0.10 on Fedora Core 1 and the dbmail-lmtpd has zombies. Any hints on where to start debugging this? # ps aux | grep Z USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1107 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1109 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1113 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1115 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1117 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1119 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1122 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1124 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1126 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1128 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1132 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1134 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1136 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1138 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 1140 0.0 0.0 0 0 ? Z Oct29 0:00 [dbmail-lmtpd <defunct>] root 2384 0.0 0.1 5552 568 pts/1 S 15:44 0:00 grep Z ---------------------------------------------------------------------- aaron - 01-Nov-06 22:30 ---------------------------------------------------------------------- In the report information it says you are running 2.1.7. Are you running plain 2.1.7 or an SVN build? At this point, 2.1.7 is really dated. We tackled some zombie issues a few months ago, and I believe that it was all work done after 2.1.7. For the 2.0 zombies, if you can turn up the logging and wait for a zombie to appear, you should be able to see what was the last thing that happened to that process. ---------------------------------------------------------------------- bjohnson - 02-Nov-06 02:27 ---------------------------------------------------------------------- No, it's really 2.1.7. I know it's dated, but I don't like running svn versions unless I have to. I was going to try to pick through the svn system to get some patches and try to apply tonight. What would be really nice is to do a 2.1.8 release real soon :) There are a lot of fixed issues that I'm interested in. ---------------------------------------------------------------------- bjohnson - 02-Nov-06 02:29 ---------------------------------------------------------------------- As far as the 2.0 lmtp zombies, is there anyway to get the info without leaving high level logging on for weeks? These usually take a long time to appear. I have zombies on the machine right now and was hoping that I could get some useful information from them. ---------------------------------------------------------------------- aaron - 02-Nov-06 02:58 ---------------------------------------------------------------------- We're probably going straight to 2.2.0, but we're having some final last issues with encodings on PostgreSQL. Hang tight for another week or two, and we'll have a stable release for you. Issue History Date Modified Username Field Change ====================================================================== 30-Oct-06 18:04 bjohnson New Issue 01-Nov-06 21:48 bjohnson Note Added: 0001516 01-Nov-06 22:30 aaron Note Added: 0001517 02-Nov-06 02:27 bjohnson Note Added: 0001518 02-Nov-06 02:29 bjohnson Note Added: 0001519 02-Nov-06 02:58 aaron Note Added: 0001520 02-Nov-06 02:59 aaron Status new => resolved 02-Nov-06 02:59 aaron Resolution open => no change required 02-Nov-06 02:59 aaron Assigned To => aaron ======================================================================
