R: Re: R: Re: R: Re: DBERROR: critical database situation
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_db: skiplist #duplicate_db: berkeley duplicate_db: skiplist 6) start imap daemon it seems quite stable. I hope it is solved. Thank you all for support! 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
Re: R: Re: R: Re: DBERROR: critical database situation
Just removing the config options that say berkeley for those two databases in
imapd.conf should do the trick (followed by nuking them again, and while Cyrus
is shut down)
Bron.
On Wed, 4 Jan 2017, at 22:08, absolutely_free--- via Info-cyrus wrote:
> 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"
> >Data: 04/01/2017 11.28
> >A: , "absolutely_f...@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
> > ---
> >
> >
> >
> >
> >
>
>
>
> 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
br...@fastmail.fm
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
Re: R: Re: DBERROR: critical database situation
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@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
br...@fastmail.fm
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
Re: R: Re: R: Re: DBERROR: critical database situation
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 important data files (which are only to delete when going the migration procedure to skiplist during that procedure). You other files still was skiplist (as your listing shows) - so they did not need that migration anymore. Did deleting tls_sessions and deliver.db (alone and by my described procedure) not helped? The error shows that there still are files within the "old" db format (i assume tls_sessions.db and deliver.db). hth a bit, good luck, Niels. -- --- Niels Dettenbach Syndicat IT & Internet http://www.syndicat.com PGP: https://syndicat.com/pub_key.asc --- signature.asc Description: This is a digitally signed message part. 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
Re: R: Re: DBERROR: critical database situation
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 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/mailman/listinfo/info-cyrus -- Bron Gondwana br...@fastmail.fm 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
R: Re: R: Re: DBERROR: critical database situation
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"
>Data: 04/01/2017 11.28
>A: , "absolutely_f...@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
> ---
>
>
>
>
>
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
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
---
signature.asc
Description: This is a digitally signed message part.
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
R: Re: DBERROR: critical database situation
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/mailman/listinfo/info-cyrus
R: Re: DBERROR: critical database situation
Hi Niels,
thank you for your reply.
I am using cyrus from sources (ports).
root@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
Re: DBERROR: critical database situation
2.4 was releasted in 2010, it's 2017. We advise not to run Berkeley DB
(even on 2.3.19), because it doesn't upgrade very nicely.
I would advise that you get some version 10 binaries and use cvt_cyrusdb
to convert all your berkeley databases to skiplist. Skiplist in 2.3.19
is rock solid. You'll need to update the config as well, but the
default for every database type in 2.3.19 is skiplist, so it's just a
matter of removing some lines from imapd.conf.
Regards,
Bron.
On Wed, 4 Jan 2017, at 19:45, absolutely_free--- via Info-cyrus wrote:
>
> 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 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 error detected; run recovery
> Jan 4 09:27:31 mail imaps[65140]: DBERROR: critical database
> situation
> Jan 4 09:27:38 mail imaps[65142]: DBERROR db5: BDB0060 PANIC: fatal
> region error detected; run recovery
> Jan 4 09:27:38 mail imaps[65142]: DBERROR: critical database
> situation
> Jan 4 09:27:38 mail master[65081]: service imaps pid 65142 in READY
> state: terminated abnormally
> Jan 4 09:27:38 mail imaps[65143]: DBERROR db5: BDB0060 PANIC: fatal
> region error detected; run recovery
> Jan 4 09:27:38 mail imaps[65143]: DBERROR: critical database
> situation
> Jan 4 09:27:38 mail master[65081]: service imaps pid 65143 in READY
> state: terminated abnormally
>
> So I stopped imapd service, and ran /usr/local/cyrus/bin/ctl_cyrusdb
> -r as cyrus user.
>
> Rebuild went fine:
>
> Jan 4 09:36:17 mail ctl_cyrusdb[62332]: recovering cyrus databases
> Jan 4 09:36:17 mail ctl_cyrusdb[62332]: done recovering cyrus
> databases
>
> and I also checked that just after ctl_cyrusdb command, I was able to
> dump mailboxes.db content with ctl_mboxlist -d
>
> After few minutes, I get same errors, and ctl_mboxlist -d returns
> nothing:
>
> cyrus@mail:/root$ /usr/local/cyrus/bin/ctl_cyrusdb -r
> cyrus@mail:/root$
>
> Yesterday I tried to:
>
> stop services
> remove and recreate /var/imap folder
> run reconstruct
>
> but it seems I got no stable solution
>
> Can you help me to solve this problem?
> Thank you very much
>
> This is my imapd.conf:
>
> root@mail:/usr/local/etc# grep -v ^# imapd.conf |grep -v ^$
> configdirectory: /var/imap
> partition-default: /var/spool/imap
> allowapop: 0
> unixhierarchysep: no
> altnamespace: no
> allowanonymouslogin: no
> allowplaintext: yes
> quotawarn: 90
> timeout: 30
> imapidlepoll: 60
> poptimeout: 10
> popminpoll: 0
> admins: root cyrus
> defaultacl: anyone lrs
> duplicatesuppression: no
> sievedir: /var/imap/sieve
> postmaster: postmaster
> sieve_maxscriptsize: 32
> sieve_maxscripts: 5
> duplicate_db: berkeley
> mboxlist_db: skiplist
> ptscache_db: berkeley
> seenstate_db: skiplist
> sasl_pwcheck_method: saslauthd
> sasl_mech_list: plain
> tls_cert_file: /etc/certs/ssl.crt/server.crt
> tls_key_file: /etc/certs/ssl.key/server.key
> tls_ca_file: /etc/certs/ssl.crt/gd_bundle-g2-g1.crt
> tls_ca_path: /etc/certs/ssl.crt
> notifysocket: /var/imap/socket/notify
>
> And cyrus.conf
>
> root@mail:/usr/local/etc# grep -v ^# cyrus.conf |grep -v ^$
> START {
> # do not delete this entry!
> recover cmd="ctl_cyrusdb -r"
> # this is only necessary if using idled for IMAP IDLE
> }
> SERVICES {
> # add or remove based on preferences
> imap cmd="imapd" listen="127.0.0.1:imap" prefork=1
> imaps cmd="imapd -s" listen="imaps" prefork=0
> #pop3 cmd="pop3d" listen="pop3" prefork=0
> pop3s cmd="pop3d -s" listen="pop3s" prefork=0
> sieve cmd="timsieved" listen="sieve" prefork=0
> # these are only necessary if receiving/exporting usenet via NNTP
> # at least one LMTP is required for delivery
> lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0
> # this is required if using notifications
> }
> EVENTS {
> # this is required
> checkpointcmd="ctl_cyrusdb -c" period=30
> # this is only necessary if using duplicate delivery suppression,
> # Sieve or NNTP
> delprune c
Re: DBERROR: critical database situation
Am Mittwoch, 4. Januar 2017, 09:45:47 CET schrieb absolutely_free--- via Info- cyrus: > 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 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 error detected; run recovery Jan 4 09:27:31 > mail imaps[65140]: DBERROR: critical database situation Jan 4 09:27:38 > mail imaps[65142]: DBERROR db5: BDB0060 PANIC: fatal region error detected; > run recovery Jan 4 09:27:38 mail imaps[65142]: DBERROR: critical database > situation Jan 4 09:27:38 mail master[65081]: service imaps pid 65142 in > READY state: terminated abnormally Jan 4 09:27:38 mail imaps[65143]: > DBERROR db5: BDB0060 PANIC: fatal region error detected; run recovery Jan > 4 09:27:38 mail imaps[65143]: DBERROR: critical database situation Jan 4 > 09:27:38 mail master[65081]: service imaps pid 65143 in READY state: > terminated abnormally Just to clearify here: it is important to follow the upgrade procedure from cyrus: https://www.cyrusimap.org/docs/cyrus-imapd/2.4.0/install-upgrade.php and to export/reimport any data during db version changes / upgrades within the used cyrus builds (export before - delete db and and reimport after). see i.e: https://lists.andrew.cmu.edu/pipermail/info-cyrus/2015-August/038316.html https://www.banquise.org/software/how-to-recover-from-cyrus-when-you-have-some-db-errors/ (Linux, but same thing...) Another thing often required in such a situation is to remove : rm -f /var/lib/cyrus/deliver.db rm -f /var/lib/cyrus/tls_sessions.db to avoid the existence of incompatible database files. If that doesn't help, a bug in your build may be a reason. Did you build the software from sources / ports or installed binaries? hth a bit, Niels. -- --- Niels Dettenbach Syndicat IT & Internet http://www.syndicat.com PGP: https://syndicat.com/pub_key.asc --- signature.asc Description: This is a digitally signed message part. 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: critical database situation
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
argumentJan 4 09:27:31 mail imaps[65141]: DBERROR: critical database
situationJan 4 09:27:31 mail imaps[65140]: DBERROR db5: BDB0060 PANIC: fatal
region error detected; run recoveryJan 4 09:27:31 mail imaps[65140]: DBERROR:
critical database situationJan 4 09:27:38 mail imaps[65142]: DBERROR db5:
BDB0060 PANIC: fatal region error detected; run recoveryJan 4 09:27:38 mail
imaps[65142]: DBERROR: critical database situationJan 4 09:27:38 mail
master[65081]: service imaps pid 65142 in READY state: terminated abnormallyJan
4 09:27:38 mail imaps[65143]: DBERROR db5: BDB0060 PANIC: fatal region error
detected; run recoveryJan 4 09:27:38 mail imaps[65143]: DBERROR: critical
database situationJan 4 09:27:38 mail master[65081]: service imaps pid 65143
in READY state: terminated abnormally
So I stopped imapd service, and ran /usr/local/cyrus/bin/ctl_cyrusdb -r as
cyrus user.
Rebuild went fine:
Jan 4 09:36:17 mail ctl_cyrusdb[62332]: recovering cyrus databasesJan 4
09:36:17 mail ctl_cyrusdb[62332]: done recovering cyrus databases
and I also checked that just after ctl_cyrusdb command, I was able to dump
mailboxes.db content with ctl_mboxlist -d
After few minutes, I get same errors, and ctl_mboxlist -d returns nothing:
cyrus@mail:/root$ /usr/local/cyrus/bin/ctl_cyrusdb -rcyrus@mail:/root$
Yesterday I tried to:
stop servicesremove and recreate /var/imap folderrun reconstruct
but it seems I got no stable solution
Can you help me to solve this problem?Thank you very much
This is my imapd.conf:
root@mail:/usr/local/etc# grep -v ^# imapd.conf |grep -v ^$configdirectory:
/var/imappartition-default: /var/spool/imapallowapop: 0unixhierarchysep:
noaltnamespace: noallowanonymouslogin: noallowplaintext: yesquotawarn:
90timeout: 30imapidlepoll: 60poptimeout: 10popminpoll: 0admins: root
cyrusdefaultacl: anyone lrsduplicatesuppression: nosievedir:
/var/imap/sievepostmaster: postmastersieve_maxscriptsize: 32sieve_maxscripts:
5duplicate_db: berkeleymboxlist_db: skiplistptscache_db: berkeleyseenstate_db:
skiplistsasl_pwcheck_method: saslauthdsasl_mech_list: plaintls_cert_file:
/etc/certs/ssl.crt/server.crttls_key_file:
/etc/certs/ssl.key/server.keytls_ca_file:
/etc/certs/ssl.crt/gd_bundle-g2-g1.crttls_ca_path:
/etc/certs/ssl.crtnotifysocket: /var/imap/socket/notify
And cyrus.conf
root@mail:/usr/local/etc# grep -v ^# cyrus.conf |grep -v ^$ START { #
do not delete this entry! recover cmd="ctl_cyrusdb -r" # this is only
necessary if using idled for IMAP IDLE}SERVICES { # add or remove based on
preferences imap cmd="imapd" listen="127.0.0.1:imap" prefork=1 imaps
cmd="imapd -s" listen="imaps" prefork=0 #pop3 cmd="pop3d"
listen="pop3" prefork=0 pop3s cmd="pop3d -s" listen="pop3s" prefork=0
sieve cmd="timsieved" listen="sieve" prefork=0 # these are only
necessary if receiving/exporting usenet via NNTP # at least one LMTP is
required for delivery lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp"
prefork=0 # this is required if using notifications}EVENTS { # this is
required checkpointcmd="ctl_cyrusdb -c" period=30 # this is only
necessary if using duplicate delivery suppression, # Sieve or NNTP delprune
cmd="cyr_expire -E 3" at=0400 # this is only necessary if caching TLS
sessions tlsprune cmd="tls_prune" at=0400}
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: critical database situation
Hi! I updated SuSE 9.2 to 9.3, i.e. cyrus 2.2.8 to 2.2.12 (and also the Berkeley DB, of course, don't know the version shipped with 9.2, I have 4.3.27 installed now). Well, this is the result: Jun 4 12:09:19 tcn master[31073]: process 1913 exited, status 75 Jun 4 12:09:19 tcn master[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 like the /var/lib/imap db is corrupted but why should it? ctl_cyrusdb didn't help either. Possibly the db format has changed? I did a db_dump file.db.old | db_load file.db the the db files but this didn't solve the problem either. I found this thread which points to a fix (!) from Apple for cyrus for OSX: http://www.afp548.com/forum/viewtopic.php?showtopic=7532 So, what's going wrong and may I fix it ASAP? TIA Timo --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
DBERROR: critical database situation
Greetings, I'm having problems with cyrus-imapd-2.2.12 and db4-4.3.27nb1 on 64-bit UltraSparc running NetBSD # uname -a NetBSD u10 3.0_BETA NetBSD 3.0_BETA (GENERIC) #1: Tue Mar 29 22:14:52 UTC 2005 [EMAIL PROTECTED]:/opt/obj.sparc64/sys/arch/sparc64/compile/GENERIC sparc64 As soon as postfix tries to deliver a message, cyrus enters a loop and starts filling up logs with the following error messages: Apr 19 20:57:18 u10 master[9254]: about to exec /usr/pkg/cyrus/bin/lmtpd Apr 19 20:57:18 u10 lmtpunix[9254]: DBERROR : db4 Apr 19 20:57:18 u10 lmtpunix[9254]: DBERROR: critical database situation Apr 19 20:57:18 u10 master[19558]: process 9254 exited, status 75 Apr 19 20:57:18 u10 master[19558]: service lmtpunix pid 9254 in READY state: terminated abnormally Apr 19 20:57:18 u10 master[7274]: about to exec /usr/pkg/cyrus/bin/lmtpd Apr 19 20:57:18 u10 lmtpunix[7274]: DBERROR : 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 i386. I can't figure out if this is a bug in db4 or cyrus. Any ideas? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
DBERROR: critical database situation
Environment: Fedora Core 1 2.4.22-1.2199.nptlsmp db4-4.1.25-14 cyrus-imapd-2.1.16 (updated after the problem to cyrus-imapd-2.1.17) Cyrus has worked flawlessly over year for me, but now out of sudden, DB crashed totally. This is what happened: --- clip --- Nov 28 04:20:06 mail ctl_cyrusdb[908]: checkpointing cyrus databases Nov 28 04:20:06 mail ctl_cyrusdb[908]: DBERROR db4: DB_LOGC->get: log record checksum mismatch Nov 28 04:20:06 mail ctl_cyrusdb[908]: DBERROR db4: DB_LOGC->get: catastrophic recovery may be required Nov 28 04:20:06 mail ctl_cyrusdb[908]: DBERROR db4: 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 error, run database recovery Nov 28 04:20:23 mail imapd[757]: DBERROR: error closing mailboxes: cyrusdb error Nov 28 04:20:23 mail imapd[757]: DBERROR db4: fatal region error detected; run recovery Nov 28 04:20:23 mail imapd[757]: DBERROR: error exiting application: DB_RUNRECOVERY: Fatal error, run database recovery Nov 28 04:20:23 mail imapd[757]: DBERROR: error exiting application: cyrusdb error --- clip --- Commands run as cyrus user: # db_stat -c db_stat: fatal region error detected; run recovery db_stat: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery # reconstruct -f reconstruct: can't initialize mboxlist environment Ouch! Suddenly, I was in big trouble. After some googling I tried this (even though this hint is for OSX): http://david.codebase.ca/index.cgi/os%20x/cyrus.writeback But in my case, it didn't start to do anything by running "reconstruct" command. I ended up restoring my imap dir from last working backups and then I was able to run "reconstruct -f" command. Ok, got it up and running, for now. Afterwards I found that using "ctl_cyrusdb -r" might have helped: http://www.kalamazoolinux.org/pipermail/members/2004-July/011219.html But what files exactly I need to delete before running "ctl_cyrusdb -r"? deliver.db ? mailboxes.db? tls_sessions.db ? db/*? I guess the cause of the problem has something to do with cyrus's weekly tasks to rotate/clean db files. Is that correct? Could someone please explaing why/what happened and how can I prevent it from happening againg? I've read from somewhere that there is a method to dump .db files into textformat and then in these cases you cound recover from those. How is this done? I could create a hourly cron job for it, just to be more safe. Best regards, Toni --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
