[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: LDAP database appears emtpy after upgrading to RH(

On Thu, Jul 03, 2003 at 11:12:00PM -0500, David Mendez wrote:
> I have what appears to be a big problem.  I recently upgraded from
> Redhat 7.2 to Redhat 9.  The upgrade went smooth, I thought, until I
> tried to access my LDAP database.  When I search I receive the
> response that it can find no entries in my database.  However, my
> database files are in /var/lib/ldap and are the correct files.   My
> configuration files are the same as before the upgrade.  Its as if
> the new ldap rpms are unable to access the information in the older
> ldap database files.  Has anyone else ran into this problem?  I am at
> a total lost for what happened and what to do.  Any help would be
> appreciated.

2.0.11 as distributed in RHL 7.2 (and subsequent updates up to 2.0.27)
used ldbm-over-gdbm to store data, but 2.0.27 as distributed in RHL 9
uses ldbm-over-bdb to store data.  You can use /usr/sbin/slapcat-gdbm to
dump the older data to LDIF and /usr/sbin/slapadd to re-import it into
the format expected by your currently-installed version of slapd.

When you do this, make sure that the permissions on the newly-created
files allow them to be accessed by a server running as the "ldap" user,
because the supplied init script starts slapd so that it will run as
that user.