On Tue, 2005-03-22 at 19:12 -0500, Todd Burroughs wrote:
It's using mbox over NFS and I've configured "mmap_disable = yes".
The mailbox that it crashed on is one of our support mailboxes and it is pretty busy. In the last 1/2 hour, it received over 100 emails.
I had a look at the code, but didn't notice anything obvious. Thanks for any help...
Here's the log messages: dovecot: Mar 22 18:22:23 Error: 19697 IMAP(support): UIDVALIDITY changed (1111532787 -> 1111533642) in mbox file /mailhome/new/s/support/mbox
This is your primary problem. Why is it changing? It sounds like Dovecot's index files aren't in NFS, and you're accessing the mbox from multiple computers with different index files?
That alone doesn't break it, but if the first message is expunged with non-Dovecot/c-client software, the UIDVALIDITY is lost and Dovecot creates a new one. But another Dovecot instance with existing index files tries to use the old UIDVALIDITY and so it complains about the change.
Is something else than Dovecot expunging the messages, or deleting/truncating the mbox entirely?
#0 0x08079f14 in mail_cache_sync_lost_handler (index=0x0) at mail-cache-sync-update.c:152 152 file_cache_invalidate(index->cache->file_cache, 0, (uoff_t)-1);
Thanks, fixed in CVS.