I conducted a scientific experiment ) I removed the unnecessary server from replication (ldap 3 ) https://pastebin.com/UaekmFfr
Then I restarted slapd on the remaining ones (ldap1 and ldap2). ldap3 deleted
Then on the new server (ldap4) I configured everything for replication.
On ldap1 added https://pastebin.com/AWjj93dT
And restarted slapd on all servers
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 ?
Is it possible to defeat this error ? ;)
23 марта 2021 г., в 20:54, Quanah Gibson-Mount <quanah@symas.commailto:quanah@symas.com> написал(а):
--On Thursday, March 18, 2021 12:27 PM +0000 Клеусов Владимир Сергеевич <Kleusov.Vladimir@wildberries.rumailto:Kleusov.Vladimir@wildberries.ru> wrote:
I'm sorry, I may have written something incomprehensible. I want to replace ldap3 with ldap4. That is, they will have different hostnames. ldap3 and ldap4 =) So I want to remove all ldap3 mentions first. Is this correct ?
The backup server needs to have the correct serverID prior to bringing it online. There's nothing that mandates changing it from the old serverID used by ldap3, and in general it's better to keep a consistent set of serverIDs rather than "retiring" one, unless you're also going to clean up your existing database of all references to the serverID being retired in the entryCSN values.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com