>On Wednesday 10 September 2008 06:18:19 Brad T Waldorf wrote:
> database bdb
> suffix "o=baseballs"
> index objectClass,sn,mail,street,pager eq
> syncrepl rid=492
dc=exampleb1,dc=com (the syncrepl searchbase) does not fit under
(the suffix of the database which holds the syncrepl statement). If
to replicate one base DN to another base DN, you should use back-ldap
rewrite rule on the consumer side, or back-relay on the provider side,
will allow you to still satisfy this restriction.
> If i modify the syncrepl statement in the slave to replicate the
> database, replication of "o=baseballs" works...
> syncrepl rid=493
Well, the if fits inside the database that holds it ...
BTW, you don't have the indexes required for syncrepl to work
what documentation did you use as the basis for this setup?
Good point Buchan, thanks for pointing this out. I've spent a bit of time
playing with indexes, mainly to see how slapindex works. For
documentation, I've used the admin guide and man pages quite a bit, as well
as googling all the errors i encounter. Specifically for indexes,
. I've found that
indexes are regenerated on certain actions (slapadd, ldapadd, and even
ldapsearch... maybe i'm wrong on that one, but it seems like it). Most of
the time, by the time i've stopped the server to slapindex (because i've
added/modified entries or whatever), the indexes are already regenerated...
so slapindex is of no consequence. Not sure what i'm missing... maybe
indexes are automatically generated on certain actions, and i've missed the
purpose of slapindex.
But anyway, in trying all this index stuff, i settled on those index values
above (index objectClass,sn,mail,street,pager eq) just for playing
purposes. I gave a quick skim of the replication chapter of the admin
guide and ctrl+f for "index", and i think i see that i should probably
include the following indexes as well?....
index objectclass,entryCSN,entryUUID eq
Sorry for not understanding this better. Thanks for your help!