[Date Prev][Date Next]
Re: unable to open Berkeley db /etc/sasldb: No such file or directory
But since last 2 months till today morning ldap was working fine. I am
not able to find the problem which could have caused this issue?
and what is the solution for this problem? Will I have to uninstall
and install new ldap with backend other than LDBM.
In my context, i am using ldap replication feature where other ldaps
has backend as LDBM. If i change backend for new ldap, will it affect
the replication feature?
Can u please tell me the command to get the version of ldap?
On 3/28/06, Quanah Gibson-Mount <firstname.lastname@example.org> wrote:
> --On Tuesday, March 28, 2006 1:00 PM +0530 Nilesh Patil
> <email@example.com> wrote:
> > Hi friends,
> > I am using openldap v 126.96.36.199 on Suse 7.2. The ldap was configured to
> > use ldbm as backend. But when i start ldap, it starts but with the
> > following message in /var/log/messages:
> > unable to open Berkeley db /etc/sasldb: No such file or directory
> There is no such version of OpenLDAP. I think you are confusing the CVS
> version string for the file with the version of OpenLDAP.
> > nowhere in the ablve file i mentioned to use berkley DB as backend.
> Of course, it is highly advised to not use the LDBM backend for a number of
> reasons. It will be removed from the OpenLDAP 2.4 release entirely.
> The /etc/sasldb issue is related to the use of SASL, not specific to
> Berkeley db, and it is likely that LDBM was compiled to use the Berkely DB
> software as the backend database storage software. Don't confuse the
> OpenLDAP "bdb" backend with Berkely DB.
> Quanah Gibson-Mount
> Principal Software Developer
> ITS/Shared Application Services
> Stanford University
> GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html