Public bug reported:
Binary package hint: dovecot-imapd
Dovecot 1.0.rc17-1ubuntu2 in Feisty crashes a lot on index files, and/or
complaints about their corruption for no reason but Dovecot's own bugs:
Jun 4 10:44:48 sanger dovecot: IMAP([EMAIL PROTECTED]): Raw backtrace: imap
[0x46a17e] -> imap [0x469f7c] -> imap [0x453268] -> imap(
mail_cache_lock+0x45) [0x445a25] -> imap [0x44798e] ->
imap(mail_cache_transaction_commit+0x2c) [0x4488ac] ->
imap(mail_index_transaction_
commit+0x42) [0x44f202] -> imap(index_transaction_commit+0x1c) [0x444d2c] ->
imap(maildir_transaction_commit+0x48) [0x424528] -> /usr/lib/
dovecot/modules/imap/lib10_quota_plugin.so [0x2ace4edab522] ->
imap(cmd_copy+0x269) [0x414929] -> imap(cmd_uid+0x48) [0x417ac8] -> imap [0
x417fa7] -> imap [0x418039] -> imap(_client_input+0x85) [0x418635] ->
imap(io_loop_handler_run+0x109) [0x46f5c9] -> imap(io_loop_run+0x18)
[0x46ea28] -> imap(main+0x3d3) [0x41fb73] ->
/lib/libc.so.6(__libc_start_main+0xf4) [0x2ace4ea6e8e4] -> imap [0x413c59]
Jun 4 10:44:48 sanger dovecot: child 23106 (imap) killed with signal 6
or:
Jun 11 18:30:03 sanger dovecot: IMAP([EMAIL PROTECTED]): Corrupted
transaction log file /var/vmail/wikimedia.org/yy/dovecot.index.log:
Append with UID 1058, but next_uid = 1059
In both of these cases, the index files corruptions must have been
caused by Dovecot itself. This makes Dovecot in Feisty rather unusable
for a production environment. The stable 1.0.0 release recently released
and now in Gutsy should fix these problems. As the Feisty packages are
in a bad shape for multiple reasons, can we get 1.0.0 (backported) in
Feisty?
** Affects: dovecot (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Dovecot crashes on index files
https://bugs.launchpad.net/bugs/119908
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
