Re: [Dovecot] Dovecot 1.1.2

[Lauri Jesmin]

Ü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

[Lauri Jesmin]

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