I followed those steps:
1) shutdown imap daemon
2) rm /var/imap/db/*
3) rm /var/imap/tls_session.db and /var/imap/deliver.db
4) reconstruct -f (as cyrus user)
5) changed /usr/local/etc/imapd.conf in this manner:
#tlscache_db: berkeley-nosync
tlscache_db: skiplist
#ptscache_db: berkeley
ptscache
t
> 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:
)
> ./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
Am Mittwoch, 4. Januar 2017, 12:08:55 CET schrieb absolutely_free--- via Info-
cyrus:
> After deleting /var/imap/db/*, /var/imap/mailboxes.db and
> /var/imap/deliver.db, it rans fine for about 20 minutes, and after:
tls_sessions and deliver.db are not important (afaik) .
Files within ./db ARE impo
Indeed, with all the right libraries. You can't upgrade libdb without
everything going to shit, which is why we have ditched BDB - the upgrade
path is bogus.
Bron.
On Wed, 4 Jan 2017, at 21:20, absolutely_free--- via Info-cyrus wrote:
>
> Hi Bron,
> thank you for you reply.
> What do y
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
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
Session
Hi Bron,thank you for you reply.What do you mean with "get some version 10
binaries"?Do you mean "binaries from FreeBSD 10"?
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
rmat, 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
DBERROR db5: BDB0061 PANIC: Invalid
> argument
> Jan 4 09:27:31 mail imaps[65141]: DBERROR: critical database
> situation
> Jan 4 09:27:31 mail imaps[65140]: DBERROR db5: BDB0060 PANIC: fatal
> region error detected; run recovery
> Jan 4 09:27:31 mail imaps[65140]: DBERROR:
ERROR db5: pthread suspend failed:
> Invalid argument Jan 4 09:27:31 mail imaps[65141]: DBERROR db5: BDB0061
> PANIC: Invalid argument Jan 4 09:27:31 mail imaps[65141]: DBERROR:
> critical database situation Jan 4 09:27:31 mail imaps[65140]: DBERROR db5:
> BDB0060 PANIC: fatal region er
Hi,I am using cyrus-imapd23-2.3.19_2 on FreeBSD.After BSD upgrade (from 10 to
11) I get problems with cyrus.I get this kind of errors on:
Jan 4 09:27:31 mail imaps[65141]: DBERROR db5: pthread suspend failed: Invalid
argumentJan 4 09:27:31 mail imaps[65141]: DBERROR db5: BDB0061 PANIC: Invalid
31073]: service imap pid 1913 in READY state:
terminated abnormally
Jun 4 12:09:19 tcn master[1914]: about to exec /usr/lib/cyrus/bin/imapd
Jun 4 12:09:19 tcn imap[1914]: DBERROR @: ^H: db4
Jun 4 12:09:19 tcn imap[1914]: DBERROR: critical database situation
(repeats forever)
Well, looks somewhat
: db4
Apr 19 20:57:18 u10 lmtpunix[7274]: DBERROR: critical database situation
Apr 19 20:57:18 u10 master[19558]: process 7274 exited, status 75
Apr 19 20:57:18 u10 master[19558]: service lmtpunix pid 7274 in READY state:
terminated
abnormally
... and so on
The same configuration works fine on i3
PANIC:
DB_RUNRECOVERY: Fatal error, run database recovery
Nov 28 04:20:06 mail ctl_cyrusdb[908]: DBERROR: critical database situation
Nov 28 04:20:23 mail imapd[757]: DBERROR db4: fatal region error
detected; runrecovery
Nov 28 04:20:23 mail imapd[757]: DBERROR: error closing: DB_RUNRECOVERY:
Fatal erro
15 matches
Mail list logo
