[csw-maintainers] Cyrus imapd update

[Rafael Ostertag]

Hi Yann

On Sat, Jan 21, 2012 at 12:00:42PM +0100, Yann Rouillard wrote:
> Le 16/01/2012 10:33, Maciej (Matchek) Blizi??ski a ??crit :
> >Looks like we need to rebuild Cyrus imapd together with sasl. I looked
> >at the current situation and found this:
> >
> >- the unstable catalog contains version 2.3.16
> >   http://mirror.opencsw.org/opencsw/unstable/i386/5.10/catalog
> >- the website declares it's at 2.4.6
> >   http://www.opencsw.org/packages/cyrus_imapd/
> >- the build recipe is at 2.4.10
> >   https://gar.svn.sourceforge.net/svnroot/gar/csw/mgar/pkg/cyrus_imapd/trunk/Makefile
> >- the newest upstream version is 2.4.13
> >   ftp://ftp.cyrusimap.org/cyrus-imapd/
> >
> >I don't know how we got into this state, but in a perfect world at
> >least the first three should match.
> >
> >Yann, can you tell what's the current situation with this package?
> >What are the main challenges in getting a new version release
> 
> Hi Maciej,
> 
> The blocker is the migration path, upgrade from 2.3 to 2.4 triggers
> a bug when berkeley is used.
> 
> I opened a bug upstream but the developper didn't have the time to
> work on it
> https://bugzilla.cyrusimap.org/show_bug.cgi?id=3496
> 

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.

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.

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

To use db_recover, issue:

 su - cyrus
 cd <imapconfigdir>
 /opt/csw/bdb(42|48)/bin/db_recover -h db


cheers
rafi