R: Re: DBERROR: critical database situation

[Niels Dettenbach]

Am Mittwoch, 4. Januar 2017, 11:18:42 CET schrieb absolutely_free--- via Info-
cyrus:
> ./tls_sessions.db: Berkeley DB (Btree, version 9, little-endian)
> ./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"?

As far as i remember, it is uncritical to just delete both files, without 
loosing "practical" data. tls_sessions just held details to ("running") TLS 
Sessions and deliver.db avoids duplicates if i remember correctly.

Stop cyrus - do a backup of delliver.db and tls_sessions.db (or just "Move it 
out of the way) for security (but i'm pretty shure that you can delete it) or 
try to just delete it and restart. 

After that try to run reconstruct -f to re-generate any indize files etc. 
within the mailboxes itself.

If that not helps, come back again. ß)

hth a bit,
best regards and good luck,

Niels.


-- 
 ---
 Niels Dettenbach
 Syndicat IT & Internet
 http://www.syndicat.com
 PGP: https://syndicat.com/pub_key.asc
 ---
 



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20170104/d7fab5a7/attachment.sig>