[Dovecot] Lots of assertion PANICs in error log

[Yates Ian Mr (ITCS)]

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 at dovecot.org
[mailto:dovecot-bounces+i.yates=uea.ac.uk at 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 at dovecot.org on behalf of
Timo Sirainen
	Sent: Sat 30/08/2008 09:37
	To: Eric Jon Rostetter
	Cc: dovecot at 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 at 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..