- dovecot - dovecot.org

[Dovecot] the most serius problems [part 1]
by Farkas Levente 30 May '03

30 May '03

hi, I try to collect out most serious problem with dovecot. so I write a series of mails:-) the first on is the load. has anybody else use dovecot in a real enviromnt with at least hundreds of users and at least 50 concurrent user at the same time? it seems to me no one else just me. the weekend I move the whole mail system to a quad P4 with 1Gb ram and this server do nothing just imap. yesterday evening I have to delete all .imap.index and other dovecot specific files. and as I wrote today morning the load was about 20-30 !!!. but even in an average day the load is over 2-3 white the cpu load is 1-2% in each of the 4 processor. the system is totaly unusable. what more today I've got other errors. of course all the time when I can't find the colution I try to escape to the latest cvs. today finally I compile a new courier install it to another port and those clients which can't connect to dovecot reconfigure to courier. but they are not compatible!!! I have to set root directory to INBOX in courier while not for dovecot and this is a real big problem. is there any way to compile dovecot to use INBOX as a root directory? since in this case at least there is a chance to switch to courier without reconfigure 300 OE6. I try to help to find out the reason for the load in any way, but it seems to me than it's better to change to courier or cyrus since our users getting angry not to mention my boss. -- Levente "Si vis pacem para bellum!"

3 7

[Dovecot] 0.99.10-test8
by Timo Sirainen 30 May '03

30 May '03

http://dovecot.procontrol.fi/test/ Again major maildir syncing updates: - uidlist file is accessed and rewritten a lot less often now than before - mail duplicates are detected and handled properly by renaming them to new base name - message flag updates and expunging before did two full syncs for cur/ directory. now it does only one. - some fixes to syncing in read-only / out-of-quota conditions - before we did always a full sync in cur/ directory when mailbox was opened. now it's done only when needed. - fixed some crash/index corruption cases I think syncing should be now very close to having perfect possible performance.

2 3

[Dovecot] new problems
by Farkas Levente 29 May '03

29 May '03

hi, so yesterday I move the whole mail system to a better machine. the only thing which is running on this system is dovect and: -------------------------------------------------- 10:44am up 6 days, 25 min, 3 users, load average: 28.03, 17.96, 9.05 233 processes: 231 sleeping, 2 running, 0 zombie, 0 stopped CPU0 states: 3.1% user, 29.4% system, 0.0% nice, 66.4% idle CPU1 states: 7.1% user, 63.2% system, 0.0% nice, 29.1% idle CPU2 states: 1.3% user, 3.1% system, 0.0% nice, 94.4% idle CPU3 states: 1.1% user, 7.4% system, 0.0% nice, 90.3% idle Mem: 1030496K av, 1021836K used, 8660K free, 0K shrd, 104064K buff Swap: 2040244K av, 55544K used, 1984700K free 776180K cached -------------------------------------------------- so the problem here is again with the load 28 (!!!)..... in the imap.log: -------------------------------------------------- imap(arvays): May 28 10:39:32 Error: Timeout while waiting for release of fcntl() lock for index file /home/arvays/Maildir/.INBOX/.imap.index imap(lfarkas): May 28 10:42:05 Panic: unreached dovecot: May 28 10:42:07 Error: child 19933 (imap) killed with signal 6 imap(ahegedus): May 28 11:05:57 Panic: file maildir-sync.c: line 472 (maildir_sync_uidlist): assertion failed: (ACTION(hash_rec) == MAILDIR_FILE_ACTION_NEW) dovecot: May 28 11:05:58 Error: child 29103 (imap) killed with signal 6 -------------------------------------------------- -- Levente "Si vis pacem para bellum!"

2 7

[Dovecot] still has error
by Farkas Levente 28 May '03

28 May '03

hi, after download the current cvs recompile, start I still has these errors: ------------------------------------- imap-login: May 28 13:49:02 Info: Login: jcsinalos [192.168.0.106] imap(jcsinalos): May 28 13:49:02 Panic: unreached dovecot: May 28 13:49:02 Error: child 31683 (imap) killed with signal 6 imap-login: May 28 13:49:03 Info: Login: jcsinalos [192.168.0.106] imap-login: May 28 13:49:03 Info: Login: jcsinalos [192.168.0.106] imap(jcsinalos): May 28 13:49:03 Panic: unreached dovecot: May 28 13:49:03 Error: child 31687 (imap) killed with signal 6 ------------------------------------- -- Levente "Si vis pacem para bellum!"

2 3

[Dovecot] 0.99.10-test7
by Timo Sirainen 28 May '03

28 May '03

- APPEND memory leak fixed - maildir syncing crash / some other errors fixed - pop3 mail fetching fixed - pop3 didn't advertise STLS in capabilities before http://dovecot.procontrol.fi/test/

1 0

[Dovecot] a few more error
by Farkas Levente 28 May '03

28 May '03

in the imap.log: imap(arvays): May 28 10:39:32 Error: Timeout while waiting for release of fcntl() lock for index file /home/arvays/Maildir/.INBOX/.imap.index imap(lfarkas): May 28 10:42:05 Panic: unreached dovecot: May 28 10:42:07 Error: child 19933 (imap) killed with signal 6 -- Levente "Si vis pacem para bellum!"

1 0

[Dovecot] serious problem
by Farkas Levente 28 May '03

28 May '03

hi, I've got dozen such errors: ---------------------------- imap-login: May 28 10:28:56 Info: Login: gpajlocz [192.168.1.182] imap(gpajlocz): May 28 10:28:56 Panic: file maildir-sync.c: line 472 (maildir_sync_uidlist): assertion failed: (ACTION(hash_rec) == MAILDIR_FILE_ACTION_NEW) dovecot: May 28 10:28:56 Error: child 17207 (imap) killed with signal 6 ---------------------------- and this users can't get into the system... -- Levente "Si vis pacem para bellum!"

1 0

[Dovecot] Dovecot 0.99.9.1 and openssl-0.9.7a-5
by Robin Whittle 28 May '03

28 May '03

Hi Timo and others, Thanks for Dovecot! I just got it running under Red Hat 9.0 after spending many hours unsuccessfully trying to get Courier IMAP to run, although I have done it in the past. Here is a compilation glitch which may already be well known: I compiled dovecot-0.99.9.1 on my newly installed and recently updated (via Red Hat Network) system and the compilation stopped due to a missing file in the SSL headers: In file included from /usr/include/openssl/ssl.h:179, from ssl-proxy-openssl.c:14: /usr/include/openssl/kssl.h:72:18: krb5.h: No such file or directory In file included from /usr/include/openssl/ssl.h:179, from ssl-proxy-openssl.c:14: The currently installed OpenSSL RPM was openssl-0.9.7a-5. This lacks the file /usr/include/openssl/krb5.h . I understand that openssl-0.9.7b is OK, but I wasn't sure about whether installing this as a tarball from http://www.openssl.org would upset any other programs on this machine, or confuse the RHN update system. I didn't really need SSL and I couldn't see a specific option for disabling it, other than a general instruction about disabling modules with a ./configure option. So I tried ./configure --help and compiled it with: ./configure --without-ssl This worked fine. I really like the report at the end of the ./configure stage saying how the program will be compiled! - Robin // Robin Whittle http://www.firstpr.com.au // Melbourne, Australia http://fondlyandfirmly.com

1 0

[Dovecot] Dovecot in OpenBSD ports system
by Andrew Basterfield 27 May '03

27 May '03

Hi I have put together dovecot port for the OpenBSD ports system. The port has yet to be submitted, but is finished awaiting testing from a wider audience. I have been using dovecot successfully on OpenBSD/sparc64 -current for months now with no problems. Would you recommend including the CR+LF patch? http://cemetery.homeunix.org/OpenBSD/dovecot.tar.gz -- http://cemetery.homeunix.org

2 6

RE: [Dovecot] Postgres "issue"
by Maikel Verheijen 27 May '03

27 May '03

Ok: a little lame to answer my own question, but I created a CRUDE patch. It does NOT check why a connection failed, it just does a PQreset, and it SEEMS to work. Kind regards, Maikel Verheijen. Ps: Timo, can something with reconnect be implemented permanently? --8<-- --- src/auth/db-pgsql.c.ORIG Tue May 27 10:06:39 2003 +++ src/auth/db-pgsql.c Tue May 27 11:16:38 2003 @@ -53,9 +53,16 @@ res = PQexec(conn->pg, query); if (PQresultStatus(res) != PGRES_TUPLES_OK) { - i_error("PGSQL: Query \"%s\" failed: %s", - query, PQresultErrorMessage(res)); - failed = TRUE; + PQreset(conn->pg); + res = PQexec(conn->pg, query); + if (PQresultStatus(res) != PGRES_TUPLES_OK) { + i_error("PGSQL: Query \"%s\" failed: %s", + query, PQresultErrorMessage(res)); + failed = TRUE; + } else { + i_error("PGSQL: Reconnected because of failure!"); + failed = FALSE; + } } else { failed = FALSE; } --8<-- -----Original Message----- From: Maikel Verheijen [mailto:maikel@ladot.com] Sent: Tuesday, May 27, 2003 9:43 AM To: 'Dovecot (E-mail)' Subject: [Dovecot] Postgres "issue" Dear list, I have a small issue with dovecot talking to a postgresql server: If my postgres server get restarted, dovecot fails to reconnect to the postgres server. I run dovecot 0.99.9.1 (which is actually a cvs version of dovecot, of may 9 2003) I have the same postgres version for the server as I use for the libraries. Is it hard to get auto-reconnect to work? Kind regards, Maikel Verheijen Ps: the log message I get is this: May 22 17:33:01 testlfw3 dovecot-auth: PGSQL: Query "SELECT password FROM aliases WHERE alias = 'maikel(a)test.com' AND password != ''" failed: FATAL 1: This connection has been terminated by the administrator. server closed the connection unexpectedly ^IThis probably means the server terminated abnormally ^Ibefore or while processing the request. Which probably describes it all :)

1 0