Anyone have any theories or experiences as to why for a certain user, some of his imap processes hang, and stay around for days and days? He just reported that his Thunderbird was timing out when trying to open folders, I looked on the server, and he had 3 old imap processes from 1 week+ ago. I killed those and his performance immediately improved. He checks mail with Thunderbird > 1.5 from both Win and Linux, Squirrelmail webmail, and pine. Of those, pine is the only one that is somewhat rare around here - any specific problems with pine's imap client code that anyone knows about? We have been using the dovecot-1.0-0.beta2.7 rpm for Fedora Core 5, I'm updating to 1.0-0.beta8.2.fc5 to see if that helps, as well. Just curious if anyone else has seen this lately. Thanks, Fran -- Fran Fabrizio Senior Systems Analyst Department of Computer and Information Sciences University of Alabama at Birmingham http://www.cis.uab.edu/ 205.934.0653
Fran Fabrizio wrote:> Anyone have any theories or experiences as to why for a certain user, > some of his imap processes hang, and stay around for days and days? He > just reported that his Thunderbird was timing out when trying to open > folders, I looked on the server, and he had 3 old imap processes from 1 > week+ ago. I killed those and his performance immediately improved. > > He checks mail with Thunderbird > 1.5 from both Win and Linux, > Squirrelmail webmail, and pine. Of those, pine is the only one that is > somewhat rare around here - any specific problems with pine's imap > client code that anyone knows about? > > We have been using the dovecot-1.0-0.beta2.7 rpm for Fedora Core 5, I'm > updating to 1.0-0.beta8.2.fc5 to see if that helps, as well. Just > curious if anyone else has seen this lately. > > Thanks, > FranI have just seen this problem, big time. I was poking around on a FreeBSD 6.1 server because of Thunderbird hangs (see thread "dovecot-1.0rc2 problems with Thunderbird" if you are interested), and I found over 900 (!) imap process. Only two users were using the dovecot server at the time. I restarted dovecot, but this did NOT kill the multitudinous imap processes. After another restart, with a 'killall imap' in the middle, things were temporarily fine, but the number of imap processes immediately started to grow again. Apparently they never exit. or use any CPU, but just sit around in KQREAD state, eventually getting swapped out. No error messages are generated.
Am 01.08.2006 um 13:34 Uhr -0500 schrieb Fran Fabrizio:>Anyone have any theories or experiences as to why for a certain >user, some of his imap processes hang, and stay around for days and >days? He just reported that his Thunderbird was timing out when >trying to open folders, I looked on the server, and he had 3 old >imap processes from 1 week+ ago. I killed those and his performance >immediately improved.Same here with NetBSD/i386 2.x. For users that have "max. cached connections" set to 1, this means effectively that they are locked out until an admin 'kill -9's the relevant imap process. Seems to be a lot better with the 1.0beta8 that I downgraded to. hauke -- /~\ The ASCII Ribbon Campaign Hauke Fath \ / No HTML/RTF in email Institut f?r Nachrichtentechnik X No Word docs in email TU Darmstadt / \ Respect for open standards Ruf +49-6151-16-3281
Hello, I'm new to the list, but I noticed a buildup of stale imap processes after upgrading to 1.0rc2. My IMAP server actually ran over maxpipekva, and I had to reboot it. I got to spend some time learning about kern.ipc.maxpipekva in the process of troubleshooting. I'm running FreeBSD 6.1-RELEASE-p3, and I have a small home office LAN setup. 2 XP client PC's, one which uses primarily Thunderbird 1.5.0.5, one which uses primarily Outlook Express. I had been running with SSL under Thunderbird (only), but disabled that in hopes of fixing the problem. It appears not to have helped. I am using the FreeBSD dovecot port, currently at rc2, with default settings. I use the default authentication scheme, and Maildir storage (my MTA is Postfix). I am running a number of other daemons on this machine but mail is its main function. I am interested in helping to solve this problem; is there anything I can do to help? Thanks, Marty
I read through the thread on Stale imap process and would like to chime in that I too am having the problem. The only imap user on the system is using Mail.app 2.1. The other users are using pop with thunderbird. After quiting mail.app and stopping dovecot I can still see many imap sessions opened. Over the course of the day a good number of imap process will be open and no one will be able to connect to the server via imap or pop. Typically I have to restart dovecot twice a day with the following: /etc/init.d/dovecot stop killall imap /etc/init.d/dovecot start I've narrowed it down to an imap issue. If i don't connect with imap the other users don't report any issues connecting with pop. I'm using mbox as my mail format on centos 4. I know that the default version on centos4 is .99, but it appears that people are still having issues into 1.0rc2. Could it have something to do with using mbox format? Mike. mbond at the-forgotten.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://dovecot.org/pipermail/dovecot/attachments/20060901/653417bf/attachment-0001.html>