Re: Replacing the server during replication
I restarted the service to be sure that the changes applied
Error in slapd logs. Please tell me what information you need to give ? I checked if I can
remove ldap4 from replication on one of the old servers and add it again. Yes, I can. The
changes are applied immediately to all servers in the replication. This means that
replication is fully working. But I do not understand what is the essence of the error in
the logs. Any help is greatly appreciated )
5 апр. 2021 г., в 20:01, Quanah Gibson-Mount <quanah(a)symas.com>
написал(а):
--On Monday, April 5, 2021 4:38 PM +0000 Клеусов Владимир Сергеевич
<Kleusov.Vladimir(a)wildberries.ru> wrote:
> Then I restarted slapd on the remaining ones (ldap1 and ldap2). ldap3
> deleted
Why did you restart them? You're using cn=config.
> Then on the new server (ldap4) I configured everything for replication.
> And restarted slapd on all servers
Same question as above
> But in the logs on the old servers (ldap1 and ldap2)
>
>
>
>
> syncrepl_null_callback : error code 0x50
> syncrepl_entry: rid=003 be_modify failed (80)
> do_syncrepl: rid=003 rc 80 retrying
>
>
> However, users are synced between servers)
>
>
> Why would such an error occur ?
You provided zero information about what the error corresponds to, so no one can answer
this question.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>