On Fri, Sep 9, 2022 at 10:31 PM Mihai Carabas <email@example.com> wrote:
On Wed, Aug 31, 2022 at 8:25 PM Mark Reynolds <firstname.lastname@example.org> wrote:
Start with the docs:
# dsconf slapd-INSTANCE repl-winsync-agmt list
# dsconf slapd-INSTANCE repl-winsync-agmt set --help
# dsconf slapd-INSTANCE repl-winsync-agmt set --host=<NEW HOSTNAME>
# dsconf slapd-INSTANCE repl-winsync-agmt init <AGREEMENT NAME>
I did this:[root@ldap ~]# dsconf slapd-ldap repl-winsync-agmt list --suffix "dc=curs,dc=xxx,dc=yy" | grep Host
But in the logs:
[09/Sep/2022:22:23:43.366356845 +0300] - INFO - NSMMReplicationPlugin - windows sync - windows_tot_run - Beginning total update of replica "agmt="cn=ad.curs.xxx.yy" (ad:636)".
And it connects to the old server (ad:636) [the old was ad.curs.xxx.yy]. From where is getting that ad?
Any input here? A reboot is needed? Dropping changelog?
Try a server restart "dsctl slapd-ldap restart". If it still pulling in that old host then maybe you have an extra/conflicting agreement? "cn=ad.curs.xxx.yy" refers the DN of the replication agreement. So check if that is the same DN of the agreement you have been modifying.
On 8/31/22 4:22 AM, Mihai Carabas wrote:
> We are planning to decommision our current PDC AD (Windows 2012R2).
> This AD is also used to sync users from our 389ds instance to this AD.
> What would be the correct procedure to update the WinSync agreement?
> Just update the hostname and run a full sync?
> Thank you,
> Mihai Carabas
> 389-users mailing list -- email@example.com
> To unsubscribe send an email to firstname.lastname@example.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://email@example.com
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Directory Server Development Team
-- Directory Server Development Team