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

2017-01-04 Thread absolutely_free--- via Info-cyrus
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

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

2017-01-04 Thread Bron Gondwana via Info-cyrus
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/mail

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

2017-01-04 Thread Niels Dettenbach via Info-cyrus
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

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

2017-01-04 Thread 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: 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 arg