R: Re: R: Re: DBERROR: critical database situation

[absolutely_free at libero.it]

After deleting /var/imap/db/*, /var/imap/mailboxes.db and /var/imap/deliver.db, 
it rans fine for about 20 minutes, and after:

Jan  4 11:58:41 mail lmtpunix[60214]: DBERROR db5: pthread suspend failed: 
Invalid argument
Jan  4 11:58:41 mail lmtpunix[60214]: DBERROR db5: BDB0061 PANIC: Invalid 
argument
Jan  4 11:58:41 mail lmtpunix[60214]: DBERROR: critical database situation
Jan  4 11:58:41 mail lmtpunix[60215]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery
Jan  4 11:58:41 mail lmtpunix[60215]: DBERROR: critical database situation
Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60215 in READY state: 
terminated abnormally
Jan  4 11:58:41 mail lmtpunix[60217]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery
Jan  4 11:58:41 mail lmtpunix[60217]: DBERROR: critical database situation
Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60217 in READY state: 
terminated abnormally
Jan  4 11:58:41 mail lmtpunix[60218]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery
Jan  4 11:58:41 mail lmtpunix[60218]: DBERROR: critical database situation
Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60218 in READY state: 
terminated abnormally
Jan  4 11:58:41 mail lmtpunix[60219]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery
Jan  4 11:58:41 mail lmtpunix[60219]: DBERROR: critical database situation
Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60219 in READY state: 
terminated abnormally
Jan  4 11:58:41 mail lmtpunix[60220]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery
Jan  4 11:58:41 mail lmtpunix[60220]: DBERROR: critical database situation
Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60220 in READY state: 
terminated abnormally
Jan  4 11:58:41 mail lmtpunix[60221]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery
Jan  4 11:58:41 mail lmtpunix[60221]: DBERROR: critical database situation
Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60221 in READY state: 
terminated abnormally


I am wondering what is my best option?
Upgrade to 2.4 (at least)?

Thank you


>----Messaggio originale----
>Da: "Niels Dettenbach" <nd at syndicat.com>
>Data: 04/01/2017 11.28
>A: <info-cyrus at lists.andrew.cmu.edu>, "absolutely_free at libero.it"
<absolutely_free at libero.it>
>Ogg: Re: R: Re: DBERROR: critical database situation
>
>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
> ---
> 
>
>
>
>