On Wed, Sep 3, 2008 at 5:38 PM, Sam Varshavchik <[EMAIL PROTECTED]> wrote: > There can be many reason, ranging from the simplest to solve -- courier-imap > has settings on the maximum number of connections accepted from the same IP > address, before dropping any more connections; to the hardest -- you're > running out of some other resource, such as the maximum number of processes > or file descriptors. The first place to look would be syslog.
I honestly cannot see anything in syslog that indicates any sort of problem is happening. I've upped MAXDAEMONS and MAXPERIP to values that are surely not being hit (but even if they were, I'd see an error in syslog, wouldn't I?). The system load average is low (below .6). I can see regular login/logout information (as I've indicated in DEBUG_LOGIN), but nothing that stands out as an error. Are there other places I can look? I've checked mail.log, daemon.log, etc. I can give you more information, such as: We're using MySQL for the virtual user tables. Postfix for the MTA. In authdaemonrc, daemons is set at 5. I've upped it to 50 before, but it made no difference. Even though MAXDAEMONS is set to 500, I rarely see "ps aux | grep imapd | wc -l" go over 200. -- Adam Olsen SendOutCards.com http://www.vimtips.org http://last.fm/user/synic ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
