Re: migration issue

[Tim Tassonis <timtas@dplanet.ch>]

Hi Jacob


One thing I had problems with is that the default backend of openldap
changed from ldbm to bdb.

But that doesn't seem to be your problem.

Another problem was that per default openldap 2.1 does not allow v2 binds,
e.g. simple binds with dn/password.

To enable them, you have to put

allow bind_v2

into your slapd.conf.


Otherwise (apart from the annoying strict structural objectclasses rules
that break just about everything), I had no problems migrating.


Bye
Tim

On Tue, 29 Apr 2003 12:37:37 -0500
jacob walcik <jwalcik@mail.utexas.edu> wrote:

> i have an existing openldap directory being served by a redhat 7.3 
> machine with openldap 2.0, and i'm wanting to migrate it to a new 
> machine running redhat 9 w/ openldap 2.1.  i've copied my slapd.conf 
> over, exported my ldap data with "slapcat > ~someuser/somefile.ldif", 
> and imported it on the new machine with "slapadd -v -f 
> "~someuser/somefile.dlif".
> 
> running "slapcat" on the new machine verifies that the data is in the 
> directory on the new machine, however i can't seem to access it via any 
> other means.  if i connect with ldapbrowser i get an error stating that 
> "List failed" (either anonymously or as the ldap administrator), and i 
> can't seem to search it w/ ldap search either.
> 
> did i do something wrong when migrating from the original machine?  is 
> there a configuration option that's changed between 2.0 and 2.1 that 
> could be causing this?
> 
> --
> jacob walcik
> jwalcik@mail.utexas.edu
>