dovecot - Aug 2008 - 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

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

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20080828/6736f48b/attachment-0002.bin>

-----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: cj.keist at colostate.edu
UNIX/Network Manager            Phone: 970-491-0630
Engineering Network Services    Fax:   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-----

-----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: cj.keist at colostate.edu
UNIX/Network Manager            Phone: 970-491-0630
Engineering Network Services    Fax:   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-----