Hi all,
We have a number of machines running Dovecot 1.2.4 that have been assert crashing occasionally. It looks like it's occurring when the users expunge their mailboxes, but I'm not sure as I can't reproduce it myself. The error in the logs is:
Oct 6 07:33:09 oh-popmap3p dovecot: imap: user=<YYYY>, rip=XXXX, pid=11931: Panic: file mail-index-view.c: line 264 (view_lookup_seq_range): assertion failed: (first_uid > 0) Oct 6 07:33:09 oh-popmap3p dovecot: imap: user=<YYYY>, rip=XXXX, pid=11931: Raw backtrace: imap [0x49e130] -> imap [0x49e193] -> imap [0x49d816] -> imap [0x47e462] -> imap(mail_index_lookup_seq+0x12) [0x47e022] -> imap(mail_index_view_sync_begin+0x36a) [0x47ffba] -> imap(index_mailbox_sync_init+0x7f) [0x45e56f] -> imap(maildir_storage_sync_init+0x100) [0x43cb70] -> imap(imap_sync_init+0x67) [0x428177] -> imap(cmd_sync_delayed+0x174) [0x4283c4] -> imap(client_handle_input+0x19e) [0x420a0e] -> imap(client_input+0x5f) [0x4213ff] -> imap(io_loop_handler_run+0xf8) [0x4a5e98] -> imap(io_loop_run+0x1d) [0x4a4fad] -> imap(main+0x620) [0x428cc0] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x323dc1d994] -> imap [0x4199f9] Oct 6 07:33:09 oh-popmap3p dovecot: dovecot: child 11931 (imap) killed with signal 6 (core dumped)
GDB stack information and some additional details are available here: http://uoregon.edu/~brandond/dovecot-1.2.4/stack.txt
We are planning to go to 1.2.6 sometime in the next week or two, but I thought I'd try to track this particular error down just in case it's still an issue after the upgrade.
-Brad