[Dovecot] Imap Timeouts
Hi guys,
I've got a client running 1.0.beta3 on SuSe 9.3
Everything has been running perfectly since it was installed about 6 months ago, but lately they've had issues with email clients not being able to connect to the IMAP server, until they close their clients(Thunderbird & Outlook) and then re-open them.
They have roughly 70 users on their network, so it sounds like it could be too many active sessions at once, but I've tried changing a few things in the config, and so far nothing has resolved this.
Any help would be appreciated.
Regards.
Neil Wilson Powered by Linux, driven by passion!
-- This email and all contents are subject to the following disclaimer: http://www.dcdata.co.za/emaildisclaimer.html
On Wed, 2006-03-22 at 16:56 +0200, Neil Wilson wrote:
Hi guys,
I've got a client running 1.0.beta3 on SuSe 9.3
Everything has been running perfectly since it was installed about 6 months ago, but lately they've had issues with email clients not being able to connect to the IMAP server, until they close their clients(Thunderbird & Outlook) and then re-open them.
For what it's worth: i'm seeing this too on our network, but _only_ with outlook clients. I haven't been able to track it down; even the dovecot debug output doesn't give any hints.
Cheers, Marc
We had occasional locking problems with 1.0-stable and Outlook, but they appear to be fixed by moving to 1.0-beta3. I migrated the rest of my users to 1.0-beta3 last night, and so far so good ...
Chris
J.M. Maurer wrote:
On Wed, 2006-03-22 at 16:56 +0200, Neil Wilson wrote:
Hi guys,
I've got a client running 1.0.beta3 on SuSe 9.3
Everything has been running perfectly since it was installed about 6 months ago, but lately they've had issues with email clients not being able to connect to the IMAP server, until they close their clients(Thunderbird & Outlook) and then re-open them.
For what it's worth: i'm seeing this too on our network, but _only_ with outlook clients. I haven't been able to track it down; even the dovecot debug output doesn't give any hints.
Cheers, Marc
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
On Wed, 2006-03-22 at 15:21 +0000, Chris Wakelin wrote:
We had occasional locking problems with 1.0-stable and Outlook, but they appear to be fixed by moving to 1.0-beta3. I migrated the rest of my users to 1.0-beta3 last night, and so far so good ...
With 1.0-beta2 we had huge problems, which were fixed in beta3 (the APPEND thingy seems to have solved a lot of issues). Still when people with outlook have their connections open (using beta3) for a few hours, it starts getting messy again.
Marc
Chris
J.M. Maurer wrote:
On Wed, 2006-03-22 at 16:56 +0200, Neil Wilson wrote:
Hi guys,
I've got a client running 1.0.beta3 on SuSe 9.3
Everything has been running perfectly since it was installed about 6 months ago, but lately they've had issues with email clients not being able to connect to the IMAP server, until they close their clients(Thunderbird & Outlook) and then re-open them.
For what it's worth: i'm seeing this too on our network, but _only_ with outlook clients. I haven't been able to track it down; even the dovecot debug output doesn't give any hints.
Cheers, Marc
I use thunderbird as well, I have two servers running beta3 (same network), one server considently gives me connect timeout errors and I have to reconnect ... there are no errors in the dovecot log and no packet /connectivity issues. I am using Freebsd 6.0 with the port release and Thunderbird 1.5
Regards, Doug
Doug Dalton wrote:
I use thunderbird as well, I have two servers running beta3 (same network), one server considently gives me connect timeout errors and I have to reconnect ... there are no errors in the dovecot log and no packet /connectivity issues. I am using Freebsd 6.0 with the port release and Thunderbird 1.5
Damn, well at least I know I'm not the only one having this problem.
Regards.
Neil Wilson Powered by Linux, driven by passion!
-- This email and all contents are subject to the following disclaimer: http://www.dcdata.co.za/emaildisclaimer.html
Chris Wakelin wrote:
We had occasional locking problems with 1.0-stable and Outlook, but they appear to be fixed by moving to 1.0-beta3. I migrated the rest of my users to 1.0-beta3 last night, and so far so good ...
Chris
I had loads of problems with older Dovecot versions, so that's why I've moved to beta3.
It's been running perfectly for a good few months, until now.
Regards.
Neil
-- This email and all contents are subject to the following disclaimer: http://www.dcdata.co.za/emaildisclaimer.html
I'm running beta3 (upgraded from beta1) on OS X 10.4.4, and we're basically seeing two problems:
total imap/dovecot crash after a period of repeated "too many files open" errors... Restarting fixes it, but we'll see if increasing the open files limit is the answer or not... Never run into this with anything before, so I'm not confident;
individual user accounts will become inaccessible occasionally when multiple clients are hitting the account at once (checking from home and work) - deleting all dovecot* files in the maildir fixes this, but... I thought Dovecot was supposed to catch this kind of thing and regenerate the files by itself? I think this is also the "locking problem" in the sense that once this occurs, the directory will fill up with lockfiles for each message the user unsuccessfully tries to load from the client side.
-deano
Neil Wilson wrote:
Chris Wakelin wrote:
We had occasional locking problems with 1.0-stable and Outlook, but they appear to be fixed by moving to 1.0-beta3. I migrated the rest of my users to 1.0-beta3 last night, and so far so good ...
Chris
I had loads of problems with older Dovecot versions, so that's why I've moved to beta3.
It's been running perfectly for a good few months, until now.
Regards.
Neil
Dean Blackburn wrote:
I'm running beta3 (upgraded from beta1) on OS X 10.4.4, and we're basically seeing two problems:
- total imap/dovecot crash after a period of repeated "too many files open" errors... Restarting fixes it, but we'll see if increasing the open files limit is the answer or not... Never run into this with anything before, so I'm not confident;
Several other people on this list have run into this problem, and I believe raising the limit has solved the issue for them.
- individual user accounts will become inaccessible occasionally when multiple clients are hitting the account at once (checking from home and work) - deleting all dovecot* files in the maildir fixes this, but... I thought Dovecot was supposed to catch this kind of thing and regenerate the files by itself? I think this is also the "locking problem" in the sense that once this occurs, the directory will fill up with lockfiles for each message the user unsuccessfully tries to load from the client side.
This really sounds like a locking issue more than index corruption. Are your INDEX and CONTROL files stored on NFS? I believe this is still discouraged, with the next version having better/safer locking.
-- Curtis Maloney cmaloney@cardgate.net
Curtis Maloney wrote:
- total imap/dovecot crash after a period of repeated "too many files open" errors... Restarting fixes it, but we'll see if increasing the open files limit is the answer or not... Never run into this with anything before, so I'm not confident;
Several other people on this list have run into this problem, and I believe raising the limit has solved the issue for them.
I don't imagine anyone has OS X Server 10.4.4 instructions for this? I tried to raise the limit via luanchctl, but the suggested "launchctl limit 512 unlimited" gave me per user/total limits of 512/12288, instead of 512/unlimited... Should I be worried? Doing the math, that seems to mean I potentially went from being able to support an unlimited number of people/processes with 256 per, to a grand total of 24.
Should I chuck launchctl, and just use ulimit manually?
- individual user accounts will become inaccessible occasionally when multiple clients are hitting the account at once (checking from home and work) - deleting all dovecot* files in the maildir fixes this, but... I thought Dovecot was supposed to catch this kind of thing and regenerate the files by itself? I think this is also the "locking problem" in the sense that once this occurs, the directory will fill up with lockfiles for each message the user unsuccessfully tries to load from the client side.
This really sounds like a locking issue more than index corruption.
Are your INDEX and CONTROL files stored on NFS? I believe this is still discouraged, with the next version having better/safer locking.
We are not (yet) using NFS, but I went ahead and chose all NFS-safe options in the config, as we do* intend on moving to NFS as soon as possible to allow for a somewhat* load-balanced server environment. Should we hold off, and if so, when can we expect a fix? ;)
Thanks,
-deano
-- Curtis Maloney cmaloney@cardgate.net
participants (6)
-
Chris Wakelin
-
Curtis Maloney
-
Dean Blackburn
-
Doug Dalton
-
J.M. Maurer
-
Neil Wilson