Re: [Dovecot] Dovecot 1.1.2, index_mailbox_set_recent_seq crash again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Looks like I'm still getting some errors: Sep 2 10:42:03 goku dovecot: [ID 107833 mail.crit] Panic: IMAP(brickner): file index-mail.c: line 1091 (index_mail_close): assertion failed: (!mail-data.destroying_stream) Is this same bug? Timo Sirainen wrote: The bug was completely elsewhere than I thought. I was just about to send a debug patch for some of you to test, but immediately after that I managed to reproduce it myself. :) So this should finally get rid of the problem: http://hg.dovecot.org/dovecot-1.1/rev/8cc0eaec7d0f - -- C. J. Keist Email: [EMAIL PROTECTED] UNIX/Network ManagerPhone: 970-491-0630 Engineering Network ServicesFax: 970-491-5569 College of Engineering, CSU Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIvYqfA29OFr7C6jcRAmBKAKDGw2MPwADyBHOBHt8RqJkexgbeGQCgtn2u d/NpW+mO95zjGkp+z0ISHa0= =S+56 -END PGP SIGNATURE-
Re: [Dovecot] Dovecot 1.1.2, index_mailbox_set_recent_seq crash again
On Sep 2, 2008, at 9:49 PM, CJ Keist wrote: Sep 2 10:42:03 goku dovecot: [ID 107833 mail.crit] Panic: IMAP(brickner): file index-mail.c: line 1091 (index_mail_close): assertion failed: (!mail-data.destroying_stream) Is this same bug? No, it's a different one, but I haven't been able to reproduce it. Are you using any plugins? Could you get a gdb backtrace of that crash? http://dovecot.org/bugreport.html PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 1.1.2, index_mailbox_set_recent_seq crash again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timo, 24hrs, and no errors so far. Thanks so much for the fix!!! Timo Sirainen wrote: The bug was completely elsewhere than I thought. I was just about to send a debug patch for some of you to test, but immediately after that I managed to reproduce it myself. :) So this should finally get rid of the problem: http://hg.dovecot.org/dovecot-1.1/rev/8cc0eaec7d0f - -- C. J. Keist Email: [EMAIL PROTECTED] UNIX/Network ManagerPhone: 970-491-0630 Engineering Network ServicesFax: 970-491-5569 College of Engineering, CSU Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIuBuHA29OFr7C6jcRAuV3AJ4kuM+4MeXvIUZEKN3e6maOYiE9MwCfQLED NitHYB3CtMYTwc0+9kkBLKY= =okcW -END PGP SIGNATURE-
Re: [Dovecot] Dovecot 1.1.2, index_mailbox_set_recent_seq crash again
The bug was completely elsewhere than I thought. I was just about to send a debug patch for some of you to test, but immediately after that I managed to reproduce it myself. :) So this should finally get rid of the problem: http://hg.dovecot.org/dovecot-1.1/rev/8cc0eaec7d0f signature.asc Description: This is a digitally signed message part
[Dovecot] Dovecot 1.1.2, index_mailbox_set_recent_seq crash again
Hi folks, after about 3 weeks without any problems, I've found this crash in yesterday's logfile (again related to index_mailbox_set_recent_seq): Aug 16 03:39:58 linux dovecot: IMAP(user1): Raw backtrace: imap [0x80cf8e0] - imap [0x80cf93a] - imap [0x80cf26c] - imap [0x809d11a] - imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] - imap(mbox_sync+0x105d) [0x80823fd] - imap [0x807a454] - imap(index_transaction_commit+0x4e) [0x809ddfe] - imap(cmd_copy+0x35f) [0x805b26f] - imap(cmd_uid+0x59) [0x805f3d9] - imap [0x805fd7c] - imap [0x805fe25] - imap [0x80605e5] - imap(client_input+0x5e) [0x80607fe] - imap(io_loop_handler_run+0x100) [0x80d7230] - imap(io_loop_run+0x28) [0x80d63c8] - imap(main+0x4a1) [0x8068321] - /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] - imap [0x805a101] I don't know what IMAP operation caused that crash. The client (Thunderbird 2.0.0.16) silently reconnected without any notification. No obvious problems since yesterday. Dovecot 1.1.2 is running on Fedora 8 Linux 32 Bit with all patches and custom OpenSSL 0.9.8h. [ output of dovecot -n ] # 1.1.2: /usr/local/dovecot/etc/dovecot.conf ssl_cert_file: /usr/local/dovecot/etc/dovecot.crt ssl_key_file: /usr/local/dovecot/etc/dovecot.key login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login mail_location: mbox:~/Mail:INBOX=/var/spool/mail/%u auth default: mechanisms: plain login digest-md5 cram-md5 passdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd userdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd Greetings, Andreas
Re: [Dovecot] Dovecot 1.1.2, index_mailbox_set_recent_seq crash again
Some minutes ago I wrote: after about 3 weeks without any problems, I've found this crash in yesterday's logfile (again related to index_mailbox_set_recent_seq): Aug 16 03:39:58 linux dovecot: IMAP(user1): Raw backtrace: imap [0x80cf8e0] - imap [0x80cf93a] - imap [0x80cf26c] - imap [0x809d11a] - imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] - imap(mbox_sync+0x105d) [0x80823fd] - imap [0x807a454] - imap(index_transaction_commit+0x4e) [0x809ddfe] - imap(cmd_copy+0x35f) [0x805b26f] - imap(cmd_uid+0x59) [0x805f3d9] - imap [0x805fd7c] - imap [0x805fe25] - imap [0x80605e5] - imap(client_input+0x5e) [0x80607fe] - imap(io_loop_handler_run+0x100) [0x80d7230] - imap(io_loop_run+0x28) [0x80d63c8] - imap(main+0x4a1) [0x8068321] - /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] - imap [0x805a101] And just again, this time with Pine 4.64 (different user) when saving a mail from INBOX to a folder: Aug 17 05:38:02 linux dovecot: IMAP(user2): Raw backtrace: imap [0x80cf8e0] - imap [0x80cf93a] - imap [0x80cf26c] - imap [0x809d11a] - imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] - imap(mbox_sync+0x105d) [0x80823fd] - imap [0x807a454] - imap(index_transaction_commit+0x4e) [0x809ddfe] - imap(cmd_copy+0x35f) [0x805b26f] - imap [0x805fd7c] - imap [0x805fe25] - imap [0x80605e5] - imap(client_input+0x5e) [0x80607fe] - imap(io_loop_handler_run+0x100) [0x80d7230] - imap(io_loop_run+0x28) [0x80d63c8] - imap(main+0x4a1) [0x8068321] - /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] - imap [0x805a101] Greetings, Andreas
Re: [Dovecot] Dovecot 1.1.2, index_mailbox_set_recent_seq crash again
Hi folks! Aug 16 03:39:58 linux dovecot: IMAP(user1): Raw backtrace: imap [0x80cf8e0] - imap [0x80cf93a] - imap [0x80cf26c] - imap [0x809d11a] - imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] - imap(mbox_sync+0x105d) [0x80823fd] - imap [0x807a454] - imap(index_transaction_commit+0x4e) [0x809ddfe] - imap(cmd_copy+0x35f) [0x805b26f] - imap(cmd_uid+0x59) [0x805f3d9] - imap [0x805fd7c] - imap [0x805fe25] - imap [0x80605e5] - imap(client_input+0x5e) [0x80607fe] - imap(io_loop_handler_run+0x100) [0x80d7230] - imap(io_loop_run+0x28) [0x80d63c8] - imap(main+0x4a1) [0x8068321] - /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] - imap [0x805a101] And just again, this time with Pine 4.64 (different user) when saving a mail from INBOX to a folder: Aug 17 05:38:02 linux dovecot: IMAP(user2): Raw backtrace: imap [0x80cf8e0] - imap [0x80cf93a] - imap [0x80cf26c] - imap [0x809d11a] - imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] - imap(mbox_sync+0x105d) [0x80823fd] - imap [0x807a454] - imap(index_transaction_commit+0x4e) [0x809ddfe] - imap(cmd_copy+0x35f) [0x805b26f] - imap [0x805fd7c] - imap [0x805fe25] - imap [0x80605e5] - imap(client_input+0x5e) [0x80607fe] - imap(io_loop_handler_run+0x100) [0x80d7230] - imap(io_loop_run+0x28) [0x80d63c8] - imap(main+0x4a1) [0x8068321] - /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] - imap [0x805a101] Additional information: Saving the mail to the given folder didn't succeed and the mail was still in the INBOX (thus, no mail lost). Once more (saving mail from INBOX to folder with Pine 4.64): Aug 17 05:43:47 linux dovecot: IMAP(user2): Raw backtrace: imap [0x80cf8e0] - imap [0x80cf93a] - imap [0x80cf26c] - imap [0x809d11a] - imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] - imap(mbox_sync+0x105d) [0x80823fd] - imap [0x807a454] - imap(index_transaction_commit+0x4e) [0x809ddfe] - imap(cmd_copy+0x35f) [0x805b26f] - imap [0x805fd7c] - imap [0x805fe25] - imap [0x80605e5] - imap(client_input+0x5e) [0x80607fe] - imap(io_loop_handler_run+0x100) [0x80d7230] - imap(io_loop_run+0x28) [0x80d63c8] - imap(main+0x4a1) [0x8068321] - /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] - imap [0x805a101] This time, the mail was successfully saved to the folder, but it was also still in the INBOX (doubled mail). Well, better than mail loss (corrupted folders) as in Dovecot 1.1.0/1.1.1. Still don't know how to reproduce this. With Thunderbird it's hard to notice at all if you don't look at the logfile all the time. Enabling mail_debug doesn't seem to give much useful information on such type of problem. Is there anything I can do to collect useful data without watching the logfile in realtime all day long? Greetings, Andreas
