"unable to open Berkeley db /etc/sasldb2" using in-directory SASL ?

["Carl Litt" <carl@execulink.com>]

This is probably a simple question but I have already reviewed the
Administrator's Guide and searched the archives.  I am testing
openldap-2.1.17 with cyrus-sasl-2.1.12 on Red Hat 7.3 and get these
errors in my syslog for any command using SASL:

SASL [conn=22] Error: unable to open Berkeley db /etc/sasldb2: No such
file or directory
ldapwhoami: Internal Error -5 in common.c near line 630

My SASL authentication (DIGEST-MD5) does work with the in-directory
secret, but why is it trying to go to /etc/sasldb2?  Isn't the point of
in-directory SASL secrets so that you don't have to create /etc/sasldb2?
If I create /etc/sasldb2 and make it readable by slapd I still get these
errors (Invalid Argument) plus it pauses for a few seconds before
proceeding.

As I said, it still works.  It more of an annoyance than a malfunction.
Is there something I should be putting in /usr/lib/sasl/Ldap.conf?  I'm
still new to cyrus-sasl-2.1, but if it matters saslauthd is running.

Thanks,
Carl Litt
Network Administrator
Execulink Internet