[Dovecot] dovecot-1.1.rc3 assertion failure in index-sync.c

Timo Sirainen tss at iki.fi
Fri Apr 25 01:44:23 EEST 2008

On Wed, 2008-04-09 at 11:11 -0700, richs at whidbey.net wrote:
> We just came across a mailbox today that, when accessed via POP3 or 
> IMAP, crashes Dovecot.  It seems to be another index-related corruption 
> issue (as removing "dovecot.index" for INBOX fixed it);
> Using POP3:
> dovecot: Apr 09 10:28:14 Warning: POP3(USERNAME): Maildir 
> /mail/USERNAME/Maildir: UIDVALIDITY changed (1145576765 -> 1207677483)

Why is the UIDVALIDITY changing? This happens if index file contains a
different UIDVALIDITY than dovecot-uidlist. Are both maildir and indexes
stored on NFS? Do you delete dovecot-uidlist sometimes?

> dovecot: Apr 09 10:28:14 Panic: POP3(USERNAME): file index-sync.c: line 
> 39 (index_mailbox_set_recent_uid): assertion failed: 
> (seq_range_exists(&ibox->recent_flags, uid))

This most likely happens because of the above. I'll see if I can get it
fixed, but it's just a side effect.

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

More information about the dovecot mailing list