On Fri, 2007-03-09 at 11:23 -0800, Dan Price wrote:
Today I've got another new crash I haven't seen before-- this is badly impacting the user in question-- since we're crashing on their inbox. This is running on our unoptimized -g only instance-- as requested yesterday.
Does it happen every time? If so, getting the mbox anonymized would help fixing this (http://wiki.dovecot.org/MboxProblems)
Should we go back to rc24?
I think that's a bad idea. It probably works even worse, and I wouldn't be surprised if it caused this crash to happen by breaking the mbox a bit.
Error: IMAP(foobar): file mbox-sync-update.c: line 458 (mbox_sync_update_header_from): assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid == mail->uid)
new_mail_ctx = {sync_ctx = 0x80477f0, mail = {uid = 1, idx_seq = 0, keywords = {buffer = 0x0, element_size = 0}, flags = 8 '\b', uid_broken = 0, from_offset = 0, body_size = 1613, offset = 116250425, space = 0}, seq = 9347, hdr_offset = 116250425, body_offset = 116251545,header_first_change = 4294967295, header_last_change = 0, header = 0x80fa698, hdr_md5_sum = "Ê\020©:Ô\021Ãî*ÉLñ\\\001\217ä", content_length = 18446744073709551615, hdr_pos = {1083, 4294967295, 4294967295, 1096, 1108}, parsed_uid = 1, last_uid_updated_value = 0, last_uid_value_start_pos = 0, have_eoh = 1, need_rewrite = 0, seen_imapbase = 0, pseudo = 0, updated = 0, recent = 0, dirty = 0, imapbase_rewrite = 0, imapbase_updated = 0}
Hmm. It looks like you have "X-UID: 1" header somewhere in the middle of the mbox, but for some reason Dovecot doesn't think it's invalid in there. I'll try to figure this out, but the anonymized mbox would make it easier.