[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: subtree replication
Hi,
I refer to the email below that was posted sometime in Jan 01. I've created
the following 3 databases and referrals as suggested but Netscape
Communicator/Address book is giving a "Failed to search 'x.x.x.x', due to
LDAP error 'Referral hop limit exceed'
" error when performing a ldap search with base "c=sg". However, command
line "ldapsearch -C -x -b "c=sg" cn=*" was able to correctly return the 2
"cn=ldapadmin" entries from db1 and db2.
Pls kindly help to review my config files below. The 3rd database "suffix
c=sg" is the db to tie db1 (org1) and db2 (org2) together.
Thanks for your advice and time.
##slapd.conf
database ldbm
suffix "o=org1"
rootdn "cn=rootdn,o=org1"
rootpw secret
directory /var/lib/ldap/org1
database ldbm
suffix "o=org2"
rootdn "cn=rootdn,o=org2"
rootpw secret
directory /var/lib/ldap/org2
database ldbm
suffix "c=sg"
rootdn "cn=rootdn,c=sg"
rootpw secret
directory /var/lib/ldap/root
#org1.ldif
dn: o=org1
objectclass: organization
o: org1
dn: cn=ldapadmin,o=org1
objectclass: person
objectclass: inetorgperson
sn: ldapadmin
cn: ldapadmin
mail: ldapadmin@org1
userpassword: secret
##org2.ldif
dn: o=org2
objectclass: organization
o: org2
dn: cn=ldapadmin,o=org2
objectclass: person
objectclass: inetorgperson
sn: ldapadmin
cn: ldapadmin
mail: ldapadmin@org2
userpassword: secret
##root.ldif
dn: c=sg
objectclass: country
c: singapore
dn: ref="x.x.x.x/o=org1",c=sg
objectclass: referral
ref: ldap://x.x.x.x/o=org1
dn: ref="x.x.x.x/o=org2",c=sg
objectclass: referral
ref: ldap://x.x.x.x/o=org2
> > > Data in server A must be hierarchically broken into 3 dbs:
> > >
> > > db-a
> > > /\
> > > / \
> > > db-b db-c
> > >
> ## slapd.conf
> database ldbm
> suffix "ou=db1,dc=domain,dc=com"
> ...
>
> database ldbm
> suffix "ou=db2,dc=domain,dc=com"
> ...
>
> database ldbm
> suffix "dc=domain,dc=com"
>
>
>
> A couple of points to make about this.
>
> o This superior DB must be listed in slapd.conf
> after the subordinate DBs
>
> o When using replication list this, you can use
> a single replogfile for all changes
>
> o You will need subordinate knowledge references
> (i.e. referrals) from the superior DN to the
> child partitions.
>