Cyrus, clusters, GFS - HA yet again

[Janne Peltonen]

On Mon, Oct 30, 2006 at 07:46:40AM -0900, Matthew Schumacher wrote:
> > --clip--
> > Oct 30 09:21:19 lcluster2 imap[10378]: login: localhost.localdomain
> > [127.0.0.1] cyrus plaintext User logged in
> > Oct 30 09:22:21 lcluster2 imap[10378]: DBERROR db4: PANIC: fatal region
> > error detected; run recovery
> > Oct 30 09:22:21 lcluster2 imap[10378]: DBERROR: critical database
> > situation
> > Oct 30 09:22:21 lcluster2 master[10368]: process 10378 exited, status 75
> > Oct 30 09:22:21 lcluster2 master[10368]: service imap pid 10378 in READY
> > state: terminated abnormally
> > --clip--
> I can't make bdb work reliably on a single host let alone the config
> your trying to run.  I would try converting that database to skiplist
> and try again.

Thanks, I gave it a try. /etc/imapd.conf:

--clip--
configdirectory: /var/lib/imap
partition-default: /var/spool/imap
admins: cyrus
sievedir: /var/lib/imap/sieve
sendmail: /usr/sbin/sendmail
hashimapspool: true
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN
tls_cert_file: /usr/share/ssl/certs/cyrus-imapd.pem
tls_key_file: /usr/share/ssl/certs/cyrus-imapd.pem
tls_ca_file: /usr/share/ssl/certs/ca-bundle.crt
annotation_db: skiplist
duplicate_db: skiplist
mboxlist_db: skiplist
ptscache_db: skiplist
quota_db: skiplist
seenstate_db: skiplist
subscription_db: skiplist
--clip--

-- I made everything a skiplist, because the error message doesn't tell
which datebase it is that gets corrupted (I tried hunting the message in
sources to make it more verbose or see when it is output, without
success - I was able to find the "critical database situation" message,
but not the previous db4 PANIC message - not even parts of it).  But I
still get the same error. Which is weird, I think, since the error
message really looks like there is a Berkeley db somewhere that gets
corrupted. Have I missed a db in my config? (I did even remember to copy
the config to both nodes...)


--Janne