Re: Cyrus IMAP 2.5.10 BerkeleyDB use?

ellie timoney <[email protected]>
Newsgroups gmane.mail.imap.cyrus
Message-ID <1487294001.1605635.883753840.5A0BC557@webmail.messagingengine.com>
On Fri, Feb 17, 2017, at 09:42 AM, Kenneth Marshall wrote:
> On Thu, Feb 16, 2017 at 04:14:38PM -0600, Dan White wrote:
> > On 02/16/17 16:10 -0600, Kenneth Marshall wrote:
> > >We are running version cyrus-imapd-2.5.10, and even though no databases
> > >in imapd.conf default to berkeleydb, something is still using it. Here
> > >are our database definitions from our imapd.conf:
> > >
> > >duplicate_db_path: /dev/shm/cyrus-imapd/duplicate_db
> > >statuscache_db_path: /dev/shm/cyrus-imapd/statuscache_db
> > >annotation_db: skiplist
> > >duplicate_db: skiplist
> > >mboxkey_db: skiplist
> > >mboxlist_db: skiplist
> > >ptscache_db: skiplist
> > >quota_db: quotalegacy
> > >seenstate_db: skiplist
> > >statuscache_db: skiplist
> > >subscription_db: flat
> > >tls_sessions_db: skiplist
> > >userdeny_db: skiplist
> > 
> > In what way is it used?
> > 
> 
> Hi Dan,
> 
> That is the problem. I do not know what or why it is being used, but
> something
> is because it had a corruption issue and started impacting IMAP
> connections.
> 
> Regards,
> Ken
> ----
> 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

Are you sure it was cyrus-imapd using it, and not sasl?  I believe sasl
can still use BDB, and if its database is corrupt then that would affect
authentications, which would affect new IMAP connections...

I have this on my system, for what it's worth:

    $sudo file /etc/sasldb2 
    /etc/sasldb2: Berkeley DB (Hash, version 9, native byte-order)

Cheers,

ellie
----
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.