On Thu, Sep 10, 2009 at 09:10:57AM +0200, Konrad Mauz wrote: > Hi all, > > I've tried to upgrade Cyrus from 2.3.8 to 2.3.15. > I compiled 2.3.15 on the same machines with the same configure call: > > ./configure --prefix=/usr/cyrus --enable-nntp \ > --enable-murder --enable-replication \ > --enable-listext --enable-netscapehack --without-bdb > > But wenn I tried to restart imapd and pop3d process generate a lot > of error messages like: > > Sep 10 06:44:11 mailsrv master[10325]: service pop3 pid 11258 in READY state: terminated abnormally > Sep 10 06:44:11 mailsrv imap[11259]: Fatal error: cyrusdb backend berkeley-nosync not supported > Sep 10 06:44:11 mailsrv pop3[11260]: Fatal error: cyrusdb backend berkeley-nosync not supported > Sep 10 06:44:11 mailsrv lmtpunix[11261]: FATAL: cyrusdb backend berkeley-nosync not supported > Sep 10 06:44:11 mailsrv imap[11262]: Fatal error: cyrusdb backend berkeley-nosync not supported > Sep 10 06:44:11 mailsrv pop3[11263]: Fatal error: cyrusdb backend berkeley-nosync not supported > Sep 10 06:44:11 mailsrv master[10325]: service imap pid 11259 in READY state: terminated abnormally > Sep 10 06:44:11 mailsrv master[10325]: service pop3 pid 11260 in READY state: terminated abnormally > Sep 10 06:44:11 mailsrv master[10325]: service lmtpunix pid 11261 in READY state: terminated abnormally > Sep 10 06:44:11 mailsrv master[10325]: service imap pid 11262 in READY state: terminated abnormally > Sep 10 06:44:11 mailsrv master[10325]: service pop3 pid 11263 in READY state: terminated abnormally > Sep 10 06:44:11 mailsrv imap[11264]: Fatal error: cyrusdb backend berkeley-nosync not supported > Sep 10 06:44:11 mailsrv pop3[11265]: Fatal error: cyrusdb backend berkeley-nosync not supported > > The relevant part in /etc/imapd.conf: > > # DB Settings > mboxlist_db: skiplist > seenstate_db: skiplist > quota_db: skiplist > duplicate_db: skiplist > annotation_db: skiplist > ptscache_db: skiplist > subscription_db: flat > tlscache_db: skiplist > > I can not find any reference to a berkley db, so I don't know why the daemons thow errors about > the missing berkeley support. The only to dbs which are berkeley-nosync by default are: > duplicate_db and tlscache_db, but I have them set to skiplist in my config. > > Can anyone tell me, which db defaultsetting is berkeley-nosync and not overwritten in my imapd.conf? > I missed the the new feature "statuscache" and statuscache_db ( since version 2.3.11 ). The db statuscache_db is by default berkeley-nosync. Thanks to Simon Matter for this usefull hint. Regards, Konrad -- Konrad Mauz Rechenzentrum Hochschule Technik, Wirtschaft und Gestaltung Braunegger-Strasse 55, D 78462 Konstanz e-mail: kmauz@xxxxxxxxxxxxxxxx Tel.: +49 7531 206-472 Fax.: +49 7531 206-153 ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
