that looks like the errors log from 1 / A doing an init of 2 / B
there should be some activity about "NOTICE - NSMMReplicationPlugin -
changelog program - _cl5ConstructRUV" between
[31/Jan/2022:13:01:38.997721794 +] - INFO - NSMMReplicationPlugin -
repl5_tot_run - Beginning total update of
Server A is ldapserver1 & Server B is ldapserver2
this is log of server B:
https://pastebin.ubuntu.com/p/f8SRb6kYn9/
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to
FYI: The logs show that ldapserver2 abruptly closed the connection after a
successful bind
It is a bit hard to say why without the ldapserver2 logs,
My guess is that the replication manager dn is missing or wrong in
ldapserver2 replica config (but the replication manager entry exists)
(so
It would be better to have errors logs (with replication debug enabled)
from both instances A and B
Also in the logs who is A and B (ldapserver1 and ldapserver2) ?
thanks
On 1/31/22 9:02 AM, Mansoor Raeesi wrote:
That is problem with CentOS paste which expires pastes within 24 hours!
you
That is problem with CentOS paste which expires pastes within 24 hours!
you may check through this link:
https://pastebin.ubuntu.com/p/ktN5HsBrNf/
Thanks
On 1/31/22 11:24, Thierry Bordaz wrote:
Hi,
It returns 404 "page not found"
regards
thierry
On 1/30/22 7:58 AM, Mansoor Raeesi
hanks for your kind reply, logging is enabled already and this is output
of log:
https://paste.centos.org/view/a39010cd
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to
Hi,
There are several possible cause why the replication agreement failed to
complete the total update. I suggest you enable replication debug log on
A and B
(https://www.port389.org/docs/389ds/FAQ/faq.html#Troubleshooting),
before retrying a total update. If it is the first time you are
