[aread]

Thanks very much for the response. Your directions were almost correct for us. Instead of making the _ldap_replicator user on the master and then copying the password to the slapd config file, I had to set up the replica and then use the password from the config file to create the user. Doing it the way Stu suggested resulted in the _ldap_replicator user not authenticating.

Thanks for the help,

Adam

[aread]

I’m having the same problem, and it seems related to sramdeen’s solution. Our replica works fine when it’s created and then never updates. Our directory server logs contain the following message, repeated every minute or so:
[code]Aug 24 11:44:01 directoryserver slapd[2800]: SASL [conn=1371] Failure: no user in database _ldap_replicator[/code]

On the replica, we get the following logged every minute:
[code]Aug 24 11:46:01 replica slapd[43394]: slap_client_connect: URI=ldap://directoryserver:389 ldap_sasl_interactive_bind_s failed (49)
Aug 24 11:46:01 replica slapd[43394]: do_syncrepl: rid=119 retrying[/code]

It looks like we need a _ldap_replicator user, and I have no idea where to create it or what privileges it would need.

Anyone with a working replication care to post the _ldap_replicator user’s details?

[Author]

Posts