[Dovecot] assertion failed

Jan-Frode Myklebust janfrode at tanso.net
Sun May 13 23:10:16 EEST 2007

On Sun, May 13, 2007 at 08:50:16PM +0300, Timo Sirainen wrote:
> Was it courier-dovecot-migrate.pl then that created those broken uidlist
> files? 

Yes, we cleaned these up manually.

> > 	deliver(xxxxx at xxxxx): file mail-index-sync-update.c: line 841 (mail_index_sync_update_index): assertion failed: (view->hdr.messages_count == map->hdr.messages_count)
> ..
> > 	deliver(xxxxxx at xxxxxx): file mail-index.c: line 983 (mail_index_sync_from_transactions): assertion failed: (hdr.messages_count == (*map)->hdr.messages_count)
> I hoped these were completely fixed in v1.0. What filesystem do you use?

IBM's GPFS on linux, which is a shared disk cluster fs.

> > The "deliver" bugs are quite bad, as they lead to incoming messages
> > getting bounced..
> Those are all assertion failures. Doesn't your MTA treat deliver crashes
> as temporary failures which are retried?

No, sorry.. postfix seems to be bouncing when deliver dies from signal

	postfix/pipe[21066]: 4D76F3B67E: to=<XXXXXXXXXXXXXXXXX at XXX.XXX>, relay=dovecot, delay=0.3, delays=0/0/0/0.3, dsn=5.3.0, status=bounced (Command died with signal 6: "/usr/local/dovecot/libexec/dovecot/deliver") 

I guess postfix doesn't really have any way of knowing how far the
delivery succeeded, but I'd prefer if postfix would freeze these


More information about the dovecot mailing list