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 segfaults in mail_cache_header_fields_get_offset
After wondering for a while, I can now reproduce your problems. The only thing I had to do was to define WORDS_BIGENDIAN on a little-endian machine. Why are you doing that? :) Er, you're right. I built a fat (multi-architecture) Dovecot executable on a big-endian PowerPC/MacOSX machine and ran it on a little-endian Intel/MacOSX machine. The configure script does not allow for the build and run systems to have different endianness. I'll find a way around that. Thanks!
Re: [Dovecot] Dovecot-1.1.2 segfaults in mail_cache_header_fields_get_offset
On Fri, 2008-08-29 at 12:58 -0500, Mike Abbott wrote: For other users I see this error before imap crashes: dovecot: Aug 29 11:45:23 Error: IMAP(user2): Rebuilding index file / Volumes/Spool/spool/user2/mail/dovecot.index: CPU architecture changed Attached are pre- and post-rebuild copies of that user's dovecot* files, and also a copy from after a second telnet session which also crashed. It's possible this is a 32/64-bit incompatibility issue (imap is a 64- bit program for me; mail might have been delivered by a 32-bit deliver or previously read by a 32-bit imap) but more likely the dovecot* files are just hosed in some way. That error message comes if CPU endianess changes (or the bit describing it in the dovecot.index file header changes). After wondering for a while, I can now reproduce your problems. The only thing I had to do was to define WORDS_BIGENDIAN on a little-endian machine. Why are you doing that? :) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot-1.1.2 segfaults in mail_cache_header_fields_get_offset
On Fri, 2008-08-29 at 12:58 -0500, Mike Abbott wrote: dovecot: Aug 29 11:24:48 Error: child 66917 (imap) killed with signal 11 --- Backtrace --- mail_cache_header_fields_get_offset + 214 Fixed: http://hg.dovecot.org/dovecot-1.1/rev/b662b2beaf12 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 1.1.2
On Mon, 2008-08-25 at 18:39 +0300, Lauri Jesmin wrote: Hello, I upgraded dovecot to 1.1.2 this weekend and i get those errors: grep dovecot /var/log/net/maillog |grep Panic | cut -d -f 11-100| sort | uniq -c | sort -rn 7547 file index-sync.c: line 39: assertion failed: (seq_range_exists(ibox-recent_flags, uid)) This should help: http://hg.dovecot.org/dovecot-1.1/rev/8cc0eaec7d0f 89 file index-mail.c: line 1091: assertion failed: (! mail-data.destroying_stream) I've seen this before, but I've really no idea how to reproduce it. Can you get a gdb backtrace from this? See http://dovecot.org/bugreport.html 18 file mbox-sync-rewrite.c: line 590: assertion failed: (mails[idx].from_offset == start_offset) Either because of an internal bug or because the mbox file changed unexpectedly. Possibly due to NFS read cache issues. 5 file ostream-file.c: line 533: assertion failed: ((size_t)ret == total_size || !fstream-file) This should help: http://hg.dovecot.org/dovecot-1.1/rev/f690d84a9fcb 5 file mbox-lock.c: line 675: assertion failed: (lock_type == F_RDLCK || mbox-mbox_lock_type != F_RDLCK) I'm not sure about this. Can you get gdb backtrace? 1 file message-parser.c: line 684: assertion failed: (ctx-part-physical_pos = ctx-input-v_offset) This should help: http://hg.dovecot.org/dovecot-1.1/rev/1d8bd4bc3038 My setup is this: 3 servers, all Solaris, running dovecot, share home directiories via NFS, mbox format mailboxes in home directories. Indexes are separate in every server, not shared via NFS. About 20 000 users total. What do you use as NFS server? Does it support nano/microsecond precision in mtimes? Could you post your dovecot -n output? You should use mail_nfs_storage=yes at least. signature.asc 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-
[Dovecot] Dovecot-1.1.2 segfaults in mail_cache_header_fields_get_offset
Dovecot 1.1.2 crashes reliably for me now on a Mac OS X machine. Here's some info: --- Telnet session --- $ telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. a login user1 password a OK Logged in. b select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1218731580] UIDs valid * OK [UIDNEXT 2] Predicted next UID b OK [READ-WRITE] Select completed. c fetch 1 rfc822.size Connection closed by foreign host. --- Error log --- dovecot: Aug 29 11:24:30 Info: imap-login: Login: user=user1, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Aug 29 11:24:33 Error: IMAP(user1): Corrupted transaction log file /Volumes/Spool/spool/user1/mail/dovecot.index.log: hdr.size too large (75497472) dovecot: Aug 29 11:24:33 Warning: IMAP(user1): fscking index file / Volumes/Spool/spool/user1/mail/dovecot.index dovecot: Aug 29 11:24:48 Error: child 66917 (imap) killed with signal 11 --- Backtrace --- mail_cache_header_fields_get_offset + 214 mail_cache_header_fields_read + 37 mail_cache_open_and_verify + 167 mail_cache_field_exists + 77 index_mail_set_seq + 306 index_storage_search_next_nonblock + 464 mailbox_search_next + 52 imap_fetch + 345 cmd_fetch + 639 client_command_input + 33 client_command_input + 463 client_handle_input + 242 client_input + 151 io_loop_handler_run + 272 io_loop_run + 39 main + 1671 start + 52 If I do the exact same telnet all over again, the imap process crashes in the same place, but without reporting the fscking index file error first. Attached are all the post-fsck dovecot* files from the user's inbox maildir. For other users I see this error before imap crashes: dovecot: Aug 29 11:45:23 Error: IMAP(user2): Rebuilding index file / Volumes/Spool/spool/user2/mail/dovecot.index: CPU architecture changed Attached are pre- and post-rebuild copies of that user's dovecot* files, and also a copy from after a second telnet session which also crashed. It's possible this is a 32/64-bit incompatibility issue (imap is a 64- bit program for me; mail might have been delivered by a 32-bit deliver or previously read by a 32-bit imap) but more likely the dovecot* files are just hosed in some way. I can provide more information if you ask soon, but I can't keep this server broken for too long. user1-post.tgz Description: Binary data user2-pre.tgz Description: Binary data user2-post.tgz Description: Binary data user2-final.tgz Description: Binary data
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
Re: [Dovecot] Dovecot 1.1.2
Ühel kenal päeval, E, 2008-08-25 kell 10:59, kirjutas CJ Keist: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lauri, This is a known bug. You can search the dovecot mailing list for assertion. I'm running on Solaris 10 and see the same errors. So far it doesn't look to be causing my users any problems. I also did apply the patch: http://hg.dovecot.org/dovecot-1.1/rev/d674c05d725d I am not sure if this patch helped, but i downgraded dovecot to 1.0.15, this does not generate new problems. It seems that UID-s break in mailboxes and then thunderbird is starting to show wrong information - UID-s in it's cache do not match those which are in real mailbox and e-mail get wrong information about user and subject. -- Lauri Jesmin [EMAIL PROTECTED] Tartu Ülikool
[Dovecot] Dovecot 1.1.2
Hello, I upgraded dovecot to 1.1.2 this weekend and i get those errors: grep dovecot /var/log/net/maillog |grep Panic | cut -d -f 11-100| sort | uniq -c | sort -rn 7547 file index-sync.c: line 39: assertion failed: (seq_range_exists(ibox-recent_flags, uid)) 89 file index-mail.c: line 1091: assertion failed: (! mail-data.destroying_stream) 18 file mbox-sync-rewrite.c: line 590: assertion failed: (mails[idx].from_offset == start_offset) 5 file ostream-file.c: line 533: assertion failed: ((size_t)ret == total_size || !fstream-file) 5 file mbox-lock.c: line 675: assertion failed: (lock_type == F_RDLCK || mbox-mbox_lock_type != F_RDLCK) 1 file message-parser.c: line 684: assertion failed: (ctx-part-physical_pos = ctx-input-v_offset) My setup is this: 3 servers, all Solaris, running dovecot, share home directiories via NFS, mbox format mailboxes in home directories. Indexes are separate in every server, not shared via NFS. About 20 000 users total. When old indexes (1.0.15) were present, mailboxes with UID validity problems did not fix themselves, but after i removed index directories in all machines, seems like it started to repair uid validity problems. The first panic seems to be tied to UID validity problems. Some locking problems may be, because i renamed index directory and created new while dovecot was running. -- Lauri Jesmin [EMAIL PROTECTED] Tartu Ülikool
Re: [Dovecot] Dovecot 1.1.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lauri, This is a known bug. You can search the dovecot mailing list for assertion. I'm running on Solaris 10 and see the same errors. So far it doesn't look to be causing my users any problems. I also did apply the patch: http://hg.dovecot.org/dovecot-1.1/rev/d674c05d725d Lauri Jesmin wrote: Hello, I upgraded dovecot to 1.1.2 this weekend and i get those errors: grep dovecot /var/log/net/maillog |grep Panic | cut -d -f 11-100| sort | uniq -c | sort -rn 7547 file index-sync.c: line 39: assertion failed: (seq_range_exists(ibox-recent_flags, uid)) 89 file index-mail.c: line 1091: assertion failed: (! mail-data.destroying_stream) 18 file mbox-sync-rewrite.c: line 590: assertion failed: (mails[idx].from_offset == start_offset) 5 file ostream-file.c: line 533: assertion failed: ((size_t)ret == total_size || !fstream-file) 5 file mbox-lock.c: line 675: assertion failed: (lock_type == F_RDLCK || mbox-mbox_lock_type != F_RDLCK) 1 file message-parser.c: line 684: assertion failed: (ctx-part-physical_pos = ctx-input-v_offset) My setup is this: 3 servers, all Solaris, running dovecot, share home directiories via NFS, mbox format mailboxes in home directories. Indexes are separate in every server, not shared via NFS. About 20 000 users total. When old indexes (1.0.15) were present, mailboxes with UID validity problems did not fix themselves, but after i removed index directories in all machines, seems like it started to repair uid validity problems. The first panic seems to be tied to UID validity problems. Some locking problems may be, because i renamed index directory and created new while dovecot was running. - -- 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 iD8DBQFIsuUGA29OFr7C6jcRAsDEAKCk62HGyMsVeJvqNmgzCkLml2Qo9wCfZJES OAUleDB2+nFRT2XLSj8YdKM= =hoCU -END PGP SIGNATURE-
[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
Re: [Dovecot] dovecot 1.1.2 assertion
On Aug 5, 2008, at 3:48 AM, Nuno Lopes wrote: Do you still have the files? You forgot to send the dovecot.index.log file. Also perhaps dovecot.index.cache could help when figuring this out (but it contains message headers so you may not want to send it to this mailing list at least). Hi, I still have them. I sent both dovecot.index and dovecot.index.log the last time, but now I've also added the cache file in a tgz. Oh. I guess that's why Mail.app showed some weird input in the mail. Anyway fixed now: http://hg.dovecot.org/dovecot-1.1/rev/d674c05d725d PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] dovecot 1.1.2 assertion
On Jul 24, 2008, at 9:22 PM, Nuno Lopes wrote: Timo Sirainen wrote: On Jul 25, 2008, at 2:36 AM, Nuno Lopes wrote: I've upgraded to last version of dovecot and am now getting the following assertions: Jul 25 00:00:34 bld3 dovecot: Panic: IMAP([EMAIL PROTECTED]): file index-sort-string.c: line 542 (index_sort_add_ids_range): assertion failed: (left_idx == 0 right_idx == rightmost_idx) Can you reproduce this? Could you send that mailbox's dovecot.index and dovecot.index.log files to me? They don't contain any sensitive information. Both bugs are fully reproducible by trying to order a given field. In the mailbox corresponding to the indexes I send you it happens every time I try to order by subject. Would you like me to send you files corresponding to the other bug or even more examples of this one if I can find them? Do you still have the files? You forgot to send the dovecot.index.log file. Also perhaps dovecot.index.cache could help when figuring this out (but it contains message headers so you may not want to send it to this mailing list at least). PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 1.1.2? plus addressing bug in dovecot 1.1.x?
On Jul 25, 2008, at 6:01 PM, Jon Fullmer wrote: I saw the release notes to Dovecot-1.1.2. Some of the fixes imply that this plus addressing anomaly that I experienced with 1.1.0 (and 1.1.1) might have been resolved with 1.1.2. Has it been? v1.1.2 supports this: b) Call deliver with -m INBOX/$mailbox from your MTA. I don't know/remember if this solves your problem though. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 1.1.2? plus addressing bug in d ovecot 1.1.x?
On Fri, 25 Jul 2008 16:01:34 -0600, Jon Fullmer [EMAIL PROTECTED] wrote: I saw the release notes to Dovecot-1.1.2. Some of the fixes imply that this plus addressing anomaly that I experienced with 1.1.0 (and 1.1.1) might have been resolved with 1.1.2. Has it been? Plus addressing and sieve delivery to namespaces with subscriptions=no are working perfectly for me now (thanks Timo).
[Dovecot] dovecot 1.1.2, another assertion failure in index-mail.c: (!mail-data.destroying_stream)
Here is the log. --- dovecot: Jul 25 07:18:35 Panic: IMAP(user): file index-mail.c: line 1091 (index_mail_close): assertion failed: (!mail-data.destroying_stream) dovecot: Jul 25 07:18:35 Error: IMAP(user): Raw backtrace: /usr/libexec/dovecot/imap [0x80f5fd4] - /usr/libexec/dovecot/imap [0x80f6877] - /usr/libexec/dovecot/imap(i_fatal+0) [0x80f6130] - /usr/libexec/dovecot/imap(index_mail_close+0xf9) [0x80a8129] - /usr/libexec/dovecot/imap [0x80a8148] - /usr/libexec/dovecot/imap(index_mail_set_seq+0x50) [0x80a8302] - /usr/libexec/dovecot/imap [0x8087e3b] - /usr/libexec/dovecot/imap(mail_set_seq+0x21) [0x80b391c] - /usr/libexec/dovecot/imap(index_storage_search_next_nonblock+0xcb) [0x80ad3e8] - /usr/libexec/dovecot/imap(mailbox_search_next_nonblock+0x26) [0x80b6a97] - /usr/libexec/dovecot/imap(mailbox_search_next+0x2c) [0x80b6a63] - /usr/libexec/dovecot/imap [0x805b757] - /usr/libexec/dovecot/imap(cmd_copy+0x1c4) [0x805b98e] - /usr/libexec/dovecot/imap(cmd_uid+0xbb) [0x80610d3] - /usr/libexec/dovecot/imap [0x8062494] - /usr/libexec/dovecot/imap [0x80626c9] - /usr/libexec/dovecot/imap [0x80627c7] - /usr/libexec/dovecot/imap [0x8062803] - /usr/libexec/dovecot/imap(client_input+0xb7) [0x8062991] - dovecot: Jul 25 07:18:35 Error: IMAP(user): /usr/libexec/dovecot/imap(io_loop_handler_run+0x17d) [0x8100630] - /usr/libexec/dovecot/imap(io_loop_run+0x35) [0x80ff8de] - /usr/libexec/dovecot/imap(main+0xe4) [0x806de1d] - /lib/libc.so.6(__libc_start_main+0xdc) [0x42bdec] - /usr/libexec/dovecot/imap [0x805a1a1] dovecot: Jul 25 07:18:35 Error: child 27074 (imap) killed with signal 6 dovecot: Jul 25 07:18:35 Error: IMAP(user): Corrupted transaction log file /mailhome/user/.imap/Trash/dovecot.index.log: record size too small (type=0x40, offset=56, size=0) dovecot: Jul 25 07:18:36 Error: IMAP(user): Corrupted transaction log file /mailhome/user/.imap/Trash/dovecot.index.log: record size too small (type=0x40, offset=56, size=0) dovecot: Jul 25 07:19:33 Error: IMAP(user): Corrupted transaction log file /mailhome/user/.imap/Trash/dovecot.index.log: record size too small (type=0x40, offset=56, size=0) dovecot: Jul 25 07:19:42 Error: IMAP(user): Corrupted transaction log file /mailhome/user/.imap/Trash/dovecot.index.log: record size too small (type=0x40, offset=56, size=0) dovecot: Jul 25 07:19:48 Warning: IMAP(user): fscking index file (in-memory index) dovecot: Jul 25 07:19:48 Error: IMAP(user): Transaction log got desynced for index (in-memory index)
[Dovecot] dovecot 1.1.2 assertion
Hi, I've upgraded to last version of dovecot and am now getting the following assertions: Jul 25 00:00:34 bld3 dovecot: Panic: IMAP([EMAIL PROTECTED]): file index-sort-string.c: line 542 (index_sort_add_ids_range): assertion failed: (left_idx == 0 right_idx == rightmost_idx) Jul 25 00:00:34 bld3 dovecot: IMAP([EMAIL PROTECTED]): Raw backtrace: imap [0x555d30f0] - imap [0x555d3157] - imap [0x555d27d8] - imap(index_sort_list_finish_string+0xe8e) [0x555a01de] - imap(index_storage_search_next_nonblock+0x432) [0x5559caa2] - imap(mailbox_search_next+0x21) [0x555a4051] - imap(imap_sort+0xdc) [0x55577d3c] - imap(cmd_sort+0x33d) [0x55570e1d] - imap(cmd_uid+0x54) [0x55571894] - imap [0x555722ac] - imap [0x55572362] - imap [0x55572b7f] - imap(client_input+0x62) [0x55572da2] - imap(io_loop_handler_run+0xf8) [0x555da0c8] - imap(io_loop_run+0x1d) [0x555d918d] - imap(main+0x462) [0x5557a552] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x2ae31494c154] - imap [0x5556c859] in another instance: Jul 25 00:08:48 bld4 dovecot: Panic: IMAP([EMAIL PROTECTED]): file index-sort-string.c: line 607 (index_sort_add_ids_range): assertion failed: (skip 0) Jul 25 00:08:48 bld4 dovecot: IMAP([EMAIL PROTECTED]): Raw backtrace: imap [0x555d30f0] - imap [0x555d3157] - imap [0x555d27d8] - imap(index_sort_list_finish_string+0xedc) [0x555a022c] - imap(index_storage_search_next_nonblock+0x432) [0x5559caa2] - imap(mailbox_search_next+0x21) [0x555a4051] - imap(imap_sort+0xdc) [0x55577d3c] - imap(cmd_sort+0x33d) [0x55570e1d] - imap(cmd_uid+0x54) [0x55571894] - imap [0x555722ac] - imap [0x55572362] - imap [0x55572b7f] - imap(client_input+0x62) [0x55572da2] - imap(io_loop_handler_run+0xf8) [0x555da0c8] - imap(io_loop_run+0x1d) [0x555d918d] - imap(main+0x462) [0x5557a552] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b64897fc154] - imap [0x5556c859] If this is not enough for you to solve it ... Some problems were solved upgrading from 1.1.1 but these ones remained. Thanks, -- Nuno
[Dovecot] dovecot 1.1.2 dbox file_dotlock_open() failed with file
Hi Timo, i have failures like with deleting a folder in the log dovecot: Jul 25 02:12:14 Error: IMAP(.com): file_dotlock_open() failed with file /usr/local/virtual/.../[EMAIL PROTECTED]//dbox-Mails/dovecot.index.log: No such file or directory with short tests i cant see any real problem folder can be created and deleted with thunderbird ( but only with tb-extra-mailbox-sep enabled ) its not a new log entry to dovecot 1.1.2 but this is first time i noticed , by near expection of the log after update, and of course i missed it by playing so much with configs -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
[Dovecot] Dovecot 1.1.2, SIGABRT on copy mail
Hi folks, with the brandnew release Dovecot 1.1.2, the daemon killed itself with signal 6 (SIGABRT) when trying to save a mail from the INBOX to another folder. The mail client is PINE 4.64. After reconnecting to the IMAP server, the mail was actually copied to the destination folder, but the original mail was still in the INBOX and not flagged as deleted. This is the panic: Jul 25 02:13:25 linux dovecot: Panic: IMAP(user2): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(ibox-recent_flags, uid)) Jul 25 02:13:25 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] Jul 25 02:13:25 linux dovecot: child 7954 (imap) killed with signal 6 Thus, the daemon died somewhere between successfully saving a copy of the mail from INBOX to the destination folder and flagging it to be deleted in the INBOX. Just a couple of minutes later, Dovecot died again. Wanted to save a message from INBOX to another folder. But this time, the message wasn't written to the destination folder. As before, the original mail in the INBOX didn't change any flags. Jul 25 02:22:07 linux dovecot: Panic: IMAP(user2): file message-parser.c: line 770 (message_parser_parse_next_block): assertion failed: (ctx-input-eof || ctx-input-closed || ctx-input-stream_errno != 0 || ctx-broken) Jul 25 02:22:07 linux dovecot: IMAP(user2): Raw backtrace: imap [0x80cf8e0] - imap [0x80cf93a] - imap [0x80cf26c] - imap(message_parser_parse_body+0) [0x80c8ba0] - imap(message_parser_parse_body+0x1e) [0x80c8bbe] - imap [0x8095120] - imap [0x809528c] - imap(index_mail_get_special+0x3a7) [0x8095757] - imap [0x8061b94] - imap(imap_fetch+0x148) [0x80620f8] - imap(cmd_fetch+0x28e) [0x805bcae] - 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] Jul 25 02:22:07 linux dovecot: child 17931 (imap) killed with signal 6 The error cannot be reproduced with these messages. They can be saved/copied now without problems back and forth. I've tried to send more mail and reproduce the problem, but no success. Works perfectly fine. 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 The problem was reported by a user who continued to work with his mail folders. I was only a few seconds too late to grab a copy of the INBOX and index files. Greetings, Andreas
Re: [Dovecot] dovecot 1.1.2 assertion
Here go the files
Timo Sirainen wrote:
On Jul 25, 2008, at 2:36 AM, Nuno Lopes wrote:
I've upgraded to last version of dovecot and am now getting the
following assertions:
Jul 25 00:00:34 bld3 dovecot: Panic: IMAP([EMAIL PROTECTED]): file
index-sort-string.c: line 542 (index_sort_add_ids_range): assertion
failed: (left_idx == 0 right_idx == rightmost_idx)
Can you reproduce this? Could you send that mailbox's dovecot.index
and dovecot.index.log files to me? They don't contain any sensitive
information.
Both bugs are fully reproducible by trying to order a given field.
In the mailbox corresponding to the indexes I send you it happens every
time I try to order by subject.
Would you like me to send you files corresponding to the other bug or
even more examples of this one if I can find them?
Thanks,
--
Nuno Lopes
dovecot.index
Description: Binary data
+ëG
[EMAIL PROTECTED] [EMAIL PROTECTED]@ JHJHJHJH Ê 0 Ë [EMAIL PROTECTED]@ ^HJH^HJH [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED] ¨ª
[EMAIL PROTECTED]@[EMAIL PROTECTED]@ +ëG ø Y Z x a È
b c l d À r u l% v °* w ô/ x D5 y : { à? | E } \J ~ °O U XZ °_ üd Lj o øt Lz ô P ¬ L § ø¤ ¨ ª © ¯ ª ä´ È· ® л ¯ ,Á ° à ± tÈ ² ÌÍ ³ Ó ´ lØ · ØÛ º á ¼ ¸ã ½ é ¾ `î À ¸ó Á H÷  ìù à ý Ä à Å 4 Æ Ç h
È ´ É Ê L [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED][EMAIL PROTECTED] [EMAIL PROTECTED]@ ÚHJHÚHØH [EMAIL PROTECTED]@ ÚHJHÚHüH [EMAIL PROTECTED]@ HJHHüH [EMAIL PROTECTED]@ HJHHÃH [EMAIL PROTECTED] [EMAIL PROTECTED]@ ÐHJHÐHÃH [EMAIL PROTECTED]@ ÐHJHÐH,H [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED],H [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Í w y { Í w y { [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]@ HJHHH [EMAIL PROTECTED]@ ¯HJH¯HH [EMAIL PROTECTED]@ ¯HJH¯HÍH [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED](* [EMAIL PROTECTED]
[EMAIL PROTECTED] 0 Í [EMAIL PROTECTED] [EMAIL PROTECTED]|6Hi6H|6Hi6H [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@ 6Hi6H6H6H [EMAIL PROTECTED]@ 6Hi6H6H6H [EMAIL PROTECTED]@ 7Hi6H7H 7H [EMAIL PROTECTED] [EMAIL PROTECTED]@ $ $ 7Hi6H7H 7HùHé [EMAIL PROTECTED]@ +ëG Í [EMAIL PROTECTED], T $ pfHÍ Á ¹ [EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED]@ +ëG Î [EMAIL PROTECTED](0 [EMAIL PROTECTED]@[EMAIL PROTECTED]
[EMAIL PROTECTED],[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]@ $ $ ü`Hü`Hý`Hý`Hý`Hû 0 Ð [EMAIL PROTECTED]@ $ $ ü`Hü`Hý`Hý`H aH+ [EMAIL PROTECTED]@ +ëG Ð [EMAIL PROTECTED] [EMAIL PROTECTED]@ $ $ 4aHaH4aHý`H aH+ [EMAIL PROTECTED] [EMAIL PROTECTED] 0 Ñ [EMAIL PROTECTED]@ $ $ aHaHaHaH aH+ [EMAIL PROTECTED]@ $ $ aHaHaHaHssH` [EMAIL PROTECTED]@ +ëG Ñ [EMAIL PROTECTED] [EMAIL PROTECTED]@ $ $ aHaHaHaHêwH [EMAIL PROTECTED]@ +ëG Ò [EMAIL PROTECTED] [EMAIL PROTECTED]@ $ $ yHyHaHaHêwH 0 Ó [EMAIL PROTECTED]@ $ $ yHyH yHyHêwH [EMAIL
