DBERROR: critical database situation

absolutely_free at libero.it absolutely_free at libero.it
Wed Jan 4 03:45:47 EST 2017


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 at mail:/root$ /usr/local/cyrus/bin/ctl_cyrusdb -rcyrus at 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 at 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 at 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  checkpoint    cmd="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}




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20170104/17a8b2ed/attachment.html>


More information about the Info-cyrus mailing list