On Fri, 2008-08-29 at 11:03 -0500, Eric Jon Rostetter wrote:

Quoting Timo Sirainen <tss@iki.fi>:

...

On Fri, 2008-08-29 at 09:49 +0100, Yates Ian Mr (ITCS) wrote:

...

I have just upgraded to dovecot 1.1.2 and am seeing lots of the following panic messages filling up the error logs:

dovecot: Aug 29 09:34:32 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid))

This patch should help: http://hg.dovecot.org/dovecot-1.1/rev/8cc0eaec7d0f

I applied that patch last night, and I'm still seeing the same errors... So unless I didn't get the patch right, there is still something amiss...

I'm hoping it's the "didn't get patch right" ;) I don't really have any other ideas right now, let's wait and see what others report..

I spoke too soon! Although the patch did reduce the numbers of Panics significantly, I'm still getting Panic messages of the kind below:

dovecot: Sep 16 09:56:46 Warning: IMAP(user): UIDVALIDITY changed (1220425974 -> 1221545790) in mbox file /mail/spool/user dovecot: Sep 16 09:56:46 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) dovecot: Sep 16 09:56:46 Error: IMAP(user): Raw backtrace: imap [0x483cd8] -> imap [0x484743] -> imap [0x483f96] -> imap(index_mailbox_set_recent_seq+0) [0x4541d0] -> imap(index_mailbox_set_recent_seq+0x43) [0x454213] -> imap [0x43c836] -> imap(mbox_sync+0x380) [0x43d220] -> imap(mbox_storage_sync_init+0x6a) [0x43d68a] -> imap(mailbox_sync+0x1c) [0x45753c] -> imap(imap_status_get+0x90) [0x420ea0] -> imap(cmd_status+0xfc) [0x419f2c] -> imap [0x41b7c3] -> imap [0x41b788] -> imap [0x41ba5a] -> imap(client_input+0x63) [0x41bc33] -> imap(io_loop_handler_run+0x109) [0x48b529] -> imap(io_loop_run+0x28) [0x48a8e8] -> imap(main+0x3f2) [0x423312] -> /lib64/tls/libc.so.6(__libc_start_main+0xdb) [0x337911c40b] -> imap [0x4157fa] dovecot: Sep 16 09:56:46 Error: child 19238 (imap) killed with signal 6

This only seems to be happening for a handfull of users.

I've just upgraded to dovecot 1.1.3 and am STILL getting these Panics. I have tried clearing the cache files but this seems to make no difference.

Any help is appreciated!

I.

From: dovecot-bounces+i.yates=uea.ac.uk@dovecot.org

[mailto:dovecot-bounces+i.yates=uea.ac.uk@dovecot.org] On Behalf Of Yates Ian Mr (ITCS) Sent: Sunday, August 31, 2008 1:21 PM To: Dovecot Mailing List Subject: RE: [Dovecot] Lots of assertion PANICs in error log

That patch certainly worked for me!
 
I unpacked dovecot 1.1.2 into a directory, copied the patch into

there and ran: patch -p1 -i patchfilename.patch Then configured and compiled/installed as normal and all was well! If you are applying the patch to a dovecot 1.1.2 source that you have already compiled from, you might want to do a "make distclean" to remove any existing compiled code that might confuse make before you configure/compile/install just to ensure the patch is compiled in. I.

From: dovecot-bounces+i.yates=uea.ac.uk@dovecot.org on behalf of

Timo Sirainen Sent: Sat 30/08/2008 09:37 To: Eric Jon Rostetter Cc: dovecot@dovecot.org Subject: Re: [Dovecot] Lots of assertion PANICs in error log

On Fri, 2008-08-29 at 11:03 -0500, Eric Jon Rostetter wrote:
> Quoting Timo Sirainen <tss@iki.fi>:
>
> > On Fri, 2008-08-29 at 09:49 +0100, Yates Ian Mr (ITCS)

wrote: > >> I have just upgraded to dovecot 1.1.2 and am seeing lots of the > >> following panic messages filling up the error logs: > >> > >> dovecot: Aug 29 09:34:32 Panic: IMAP(user): file index-sync.c: line 39 > >> (index_mailbox_set_recent_uid): assertion failed: > >> (seq_range_exists(&ibox->recent_flags, uid)) > > > > This patch should help: > > http://hg.dovecot.org/dovecot-1.1/rev/8cc0eaec7d0f > > I applied that patch last night, and I'm still seeing the same errors... > So unless I didn't get the patch right, there is still something amiss...

I'm hoping it's the "didn't get patch right" ;) I don't really

have any other ideas right now, let's wait and see what others report..

Quoting Eric Jon Rostetter <eric.rostetter@physics.utexas.edu>:

Quoting Timo Sirainen <tss@iki.fi>:

...

...

dovecot: Aug 29 09:34:32 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid))

This patch should help: http://hg.dovecot.org/dovecot-1.1/rev/8cc0eaec7d0f

I applied that patch last night, and I'm still seeing the same errors... So unless I didn't get the patch right, there is still something amiss...

As way of an update, I could never fix this with 1.1.2, but I recently upgraded to 1.1.3 and I'm still seeing the problem, but A LOT less...

Right now, since upgrading to 1.1.3, I have 1 user, and only 1 user,
triggering this same assert.

I have two other users who each triggered another assert a single time each:

dovecot: Panic: IMAP(user): file message-parser.c: line 129
(message_parser_read_more): assertion failed: (ctx->input->eof ||
ctx->input->stream_errno != 0)

I also get the occasional error of "Next message unexpectedly lost from ..." for some users.

The one user still getting the original assert issue gets it a lot. So if you want files for this user, or more complete log entries, let me know what to do, etc...

So far I've got no user complaints about these issues. Just log entries... Funny that he wouldn't report a problem since it is a panic... One thing I note about this user, which is unique to him, is that he runs "xbiff" to monitor his mail. One might speculate the bug is being tickled by xbiff, since he is the only one running xbiff, and he is the only logging this assert message. Note with 1.1.2 I got this error for lots and lots of users; but so far with 1.1.3 it is only this single user.

-- Eric Rostetter The Department of Physics The University of Texas at Austin

This message is provided "AS IS" without warranty of any kind, either expressed or implied. Use this message at your own risk.

-- Eric Rostetter The Department of Physics The University of Texas at Austin

This message is provided "AS IS" without warranty of any kind, either expressed or implied. Use this message at your own risk.

Timo Sirainen wrote:

...

I also get the occasional error of "Next message unexpectedly lost from ..." for some users.

I've added some debugging code to my code to figure out why this is happening. Unfortunately I've been reading my mails over a week without it happening..

We've been seeing this for a few users also with both 1.1.3 and 1.1.4. When it happens, the user can still see the mail in all clients EXCEPT Outlook, where it shows up as some permeation of blank headers/good body, no body/good headers, etc.

This has only happened to mbox users, same as others who've reported it. It is reproducible for a given message; if the user logs out of Outlook and back in, it still shows up "malformed". But: using pine or mutt to bounce the message results in a message that does NOT trigger the problem for the bounce recipient.

Any thoughts, Timo? We're hesitating to go live with the 1.1x series for this reason. We could just convert affected folks to Maildir, but we're not really ready for that conversion on a large scale yet.

-Brian