[Dovecot] Corrupted Indexes + other errors in logs

Timo Sirainen tss at iki.fi
Thu Aug 10 22:21:26 EEST 2006

On Tue, 2006-07-11 at 23:52 +0300, Dumitru Negara wrote:
> Jul 10 13:52:35 mailserv dovecot: imap-login: file ioloop.c: line 22 
> (io_add): assertion failed: (fd >= 0)
> Jul 10 13:52:35 mailserv dovecot: child 2451 (login) killed with signal 6

Well, it would be nice to know why this happens. Unfortunately it's a
bit difficult to debug login processes. How often does this happen? Do
you know how to reproduce it?

Do you use SSL? Or Dovecot's proxying feature?

> ...
> Jul 10 16:02:22 mailserv dovecot: IMAP(user1): Corrupted transaction log 
> file /var/mail/user1/.propuri.29-06_Q01388458-15/dovecot.index.log: 
> Append with UID 1, but next_uid = 20
> ...

It's possible that I did some fixes related to this since rc2, but I'm
not sure. Again if you know how to reproduce would be nice..

> Jul 10 16:23:18 mailserv dovecot: IMAP(user2): Corrupted index cache 
> file /var/mail/user12/.Sent/dovecot.index.cache: record points outside file

This is completely transparent to users, but I thought I had already
fixed all these problems. Or are you using NFS?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : http://dovecot.org/pipermail/dovecot/attachments/20060810/d4e38c7c/attachment.pgp 

More information about the dovecot mailing list