On Sat, Apr 12, 2003 at 06:04:32PM +0300, Timo Sirainen
wrote:> Expunging messages caused those "Corrupted index file" errors.
That's
> fixed now. There's probably still some problems, at least this fix
> didn't fix any crashes..
>
> test3 available from http://dovecot.procontrol.fi/test/
Hi-
Tried this- still get at least three varieties of the "Corrupted index
file" errors (very frequent as you can see by the timestamps):
Apr 14 23:48:03 mercury mem[11546]: pop3(user3): Corrupted index file
/users/1d/user3/Maildir/.INBOX/.imap.index: Filename mismatch for UID
1366: 1050157920.28714.mercury.mv.net vs 1050168692.1692.mercury.mv.net
Apr 14 23:48:11 mercury mem[11880]: pop3(user4): Corrupted index file
(in-memory index for /users/2a/user4/Maildir): Filename mismatch for
UID 1: 1050378453.254 31.mercury.mv.net vs 1050378419.24825.mercury.mv.net
Apr 14 23:48:15 mercury mem[10327]: pop3(user1): Corrupted index file
/users/8f/user1/Maildir/.INBOX/.imap.index: index.next_uid (118) >
uidlist.next_uid (114)
Plus very rapid signal 11s:
Apr 14 23:48:12 mercury dovecot: child 25983 (imap) killed with signal 11
Apr 14 23:48:12 mercury dovecot: child 25992 (imap) killed with signal 11
Apr 14 23:48:14 mercury dovecot: child 26034 (imap) killed with signal 11
Pretty much the same as with test2.
All occurances of this last mesasge say "(imap)" -- no
"pop3".
However most accesses on this system are pop3, not imap.
In fact it appears that all examples of "Corrupted index" are pop3
instances, and all examples of "signal 11" are imap..
I tried setting
mail_drop_priv_before_exec = yes
as you suggested, to generate a core dump, but if it's dumping core
I can't find it anywhere. dovecot was started from /var/tmp and
I have verified that the running dovecot and dovecot-auth processes
have /var/tmp as a working directory.
I also continue to see sporadic "(imap) returned error 89" with this
version and with 0.99.8.1
-mm-