high-availability Cyrus (i.e. glusterfs)?

[Andrew Morgan]

On Wed, 29 Sep 2010, Tomasz Chmielewski wrote:

> Hmm - I added this to imapd.conf:
>
> annotation_db: skiplist
> duplicate_db: skiplist
> mboxlist_db: skiplist
> ptscache_db: skiplist
> quota_db: skiplist
> seenstate_db: skiplist
> tlscache_db: skiplist
>
>
> When starting cyrus, I have this:
>
> Sep 29 02:53:48 omega cyrus/master[1089]: process started
> Sep 29 02:53:48 omega cyrus/ctl_cyrusdb[1090]: recovering cyrus databases
> Sep 29 02:53:48 omega cyrus/ctl_cyrusdb[1090]: done recovering cyrus databases
> Sep 29 02:53:49 omega cyrus/cyr_expire[1091]: DBERROR db4: Program version 4.2 doesn't match environment version
> Sep 29 02:53:49 omega cyrus/cyr_expire[1091]: DBERROR: dbenv->open '/shared/var/lib/cyrus/db' failed: Invalid argument
> Sep 29 02:53:49 omega cyrus/cyr_expire[1091]: DBERROR: init() on berkeley
> Sep 29 02:53:49 omega cyrus/cyr_expire[1091]: duplicate_prune: pruning back 3 days
> Sep 29 02:53:49 omega cyrus/cyr_expire[1091]: duplicate_prune: purged 0 out of 0 entries
> Sep 29 02:53:49 omega cyrus/cyr_expire[1091]: expunged 0 out of 0 messages from 0 mailboxes
> Sep 29 02:53:49 omega cyrus/tls_prune[1092]: tls_prune: purged 0 out of 0 entries
> Sep 29 02:53:49 omega cyrus/master[1089]: ready for work
> Sep 29 02:53:49 omega cyrus/ctl_cyrusdb[1093]: checkpointing cyrus databases
> Sep 29 02:53:49 omega cyrus/ctl_cyrusdb[1093]: done checkpointing cyrus databases
>
>
> # file /shared/var/lib/cyrus/db/*
> /shared/var/lib/cyrus/db/__db.001:       data
> /shared/var/lib/cyrus/db/__db.002:       data
> /shared/var/lib/cyrus/db/__db.003:       data
> /shared/var/lib/cyrus/db/__db.004:       data
> /shared/var/lib/cyrus/db/__db.005:       data
> /shared/var/lib/cyrus/db/log.0000000001: Berkeley DB (Log, version 8, native byte-order)
> /shared/var/lib/cyrus/db/skipstamp:      data
>
>
> The error and "Berkeley DB" log file is there even if I empty this 
> directory, and start Cyrus.
>
> Did I miss some value in imapd.conf?

Cyrus is always linked with Berkeley DB, so it always tries to init the 
Berkeley DB environment.  Even with all your backends set to "skiplist", 
you'll still see the Berkeley DB log files in {configdir}/db/.  You can 
safely ignore them.

I'm not sure why you still get Berkeley DB errors when starting Cyrus.  I 
have converted everything to skiplist, and I do not get those errors.

 	Andy