[csw-maintainers] Cyrus imapd update

Yann Rouillard yann at pleiades.fr.eu.org
Sat Jan 28 13:12:00 CET 2012

Hi Rafael,

Le 25/01/2012 07:39, Rafael Ostertag a écrit :
> I tested the new cyrus package with the config attached to the above 
> mentioned
> bug report, and it does not seem to exhibit the behavior described anymore.
That's good !
I tested again and was able to reproduce it again with cyrus linked with 
Berkeledy db 4.2 (in my repository).
So I suppose berkeleydb 4.8 is better at handling this case.

> However, I hit another bug/error during testing. After upgrading from 2.3 to
> 2.4 it might happen that ctl_cyrusdb dies:
> Jan 22 10:42:41 cswtest master[7103]: [ID 965400 local6.notice] process started
> Jan 22 10:42:41 cswtest master[7108]: [ID 392559 local6.debug] about to exec /opt/csw/sbin/ctl_cyrusdb
> Jan 22 10:42:41 cswtest ctl_cyrusdb[7108]: [ID 866726 local6.warning] DBERROR db4: Program version 4.8 doesn't match environment version 4333.0
> Jan 22 10:42:45 cswtest genunix: [ID 603404 kern.notice] NOTICE: core_log: ctl_cyrusdb[7108] core dumped: /var/cores/core.ctl_cyrusdb.7108
> This error is reproducible (at least for me on Sol10x): first, send a few
> hundred mails to cyrus 2.3, then upgrade to 2.4.
If it is rerpoducible, we might open a bug upstream.
Can you send the me a tar.gz of the config directory which triggers the 
bug ?

> By using the db_recover utility, I was able to salvage the database and cyrus
> started normally.
> Depending on the database configuration in imapd.conf, one has to either use
> db_recover from bdb 4.2 or 4.8:
> BDB ->  Skiplist: db_recover 4.8
> BDB ->  BDB: db_recover 4.2

Hmm, the problem is that you might have a user which has both BDB -> BDB 
and BDB -> Skiplist migration.
We might try to always launch db_recover 4.2 then db_recover 4.8, did 
you try to call them both in your tests ?


More information about the maintainers mailing list