[Date Prev][Date Next]
Re: unable to open Berkeley db /etc/sasldb: No such file or directory
--On Tuesday, March 28, 2006 4:02 PM +0530 Nilesh Patil
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?
As I noted, LDBM is inherently unstable. It can and will corrupt data
without notifying the end user.
and what is the solution for this problem? Will I have to uninstall
and install new ldap with backend other than LDBM.
I would see if you could export the database (via slapcat). Hopefully it
is in a state where you can rescue your data.
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?
No, but I'd upgrade those systems when possible as well.
Can u please tell me the command to get the version of ldap?
Principal Software Developer
ITS/Shared Application Services
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html