Re: cyrus 2.4 and DBERROR

Anthony Prades via Info-cyrus <[email protected]>
Newsgroups gmane.mail.imap.cyrus
Message-ID <[email protected]>
Hi,

Try db_recover tool in /var/lib/cyrus, somithing like (depends of your 
install):
-- stop cyrus --
cd /var/lib/cyrus && db_recover -v -h /var/lib/cyrus/db
-- start cyrus --

or herder version:
-- stop cyrus --
cd /var/lib/cyrus && db_recover -c -v -h /var/lib/cyrus/db
-- start cyrus --

If problem persists, you may convert your db file to flat, then flat to 
db using cvt_cyrusdb tool - something like:
-- stop cyrus --
cvt_cyrusdb /var/lib/cyrus/mailboxes.db skiplist /tmp/mailboxes flat
mv /var/lib/cyrus/mailboxes.db /var/lib/cyrus/mailboxes.db.orig
cvt_cyrusdb /tmp/mailboxes flat /var/lib/cyrus/mailboxes.db skiplist
chown cyrus:mail /var/lib/cyrus/mailboxes.db
-- start cyrus --

Note: do backup before...

Anthony

On 12/1/18 8:20 AM, chose wrote:
>  Good morning,
>  what caused this and how to recover. All files in db/ directory were 
> deleted and cyrus restarted, still no progress.
>
> Dec  1 07:57:44 email11 imap[4498]: DBERROR db4: PANIC: fatal region 
> error detected; run recovery
> Dec  1 07:57:44 email11 imap[4498]: DBERROR: critical database situation
> Dec  1 07:57:44 email11 idled[4422]: DBERROR db4: PANIC: fatal region 
> error detected; run recovery
> Dec  1 07:57:44 email11 idled[4422]: DBERROR: critical database situation
> Dec  1 07:57:44 email11 imap[4428]: DBERROR db4: PANIC: fatal region 
> error detected; run recovery
> Dec  1 07:57:44 email11 imap[4428]: DBERROR: critical database situation
> Dec  1 07:57:44 email11 imap[4482]: DBERROR db4: PANIC: fatal region 
> error detected; run recovery
>
>   Cyrus imap is working, but it si slow.
>   Thanks and best regards
>   J.Karliak
>
----
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.