R: Re: DBERROR: critical database situation

[Bron Gondwana]

Oh good, you can just delete those two BDB files with Cyrus shut down (and change them to skiplist while you're at it!)

Once you've done that you can delete everything in the $confdir/db folder too.

(delete might mean take a copy somewhere else until you're happy everything is working of course)

They're both things that don't matter across restarts.

Bron.

On Wed, 4 Jan 2017, at 21:18, absolutely_free--- via Info-cyrus wrote:
> Hi Niels,
> 
> thank you for your reply.
> I am using cyrus from sources (ports).
> 
> root at mail:/var/imap# find . -name "*.db" -exec file '{}' \;
> ./mailboxes.db: Cyrus skiplist DB
> ./annotations.db: Cyrus skiplist DB
> ./db.backup1/annotations.db: Cyrus skiplist DB
> ./db.backup1/mailboxes.db: Cyrus skiplist DB
> ./tls_sessions.db: Berkeley DB (Btree, version 9, little-endian)
> ./db.backup2/annotations.db: Cyrus skiplist DB
> ./db.backup2/mailboxes.db: Cyrus skiplist DB
> ./deliver.db: Berkeley DB (Btree, version 9, little-endian)
> 
> So, I can convert tls_sessions and deliver db to skiplist format, right?
> How can I determine which database is giving me "DBERROR: critical database 
> situation"?
> 
> Thank you
> 
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus


-- 
  Bron Gondwana
  brong at fastmail.fm