0

We have 3 IPA servers, ns01, ns02, ns03. Had some issues with ns03 about a month back and had to recreate the VM. We thought we had recreated and set it back up correctly however we discovered today that it was not replicating. All new users and servers were put into ns03 and did not replicate over to ns01/02. ns01/02 are replicating with each other without issue.

Goal: Repair replication of ns03 to ns01/02. ns03 has the correct data.

[root@ns03 ~]# ipa-replica-manage list -v ns03.vns.local
Directory Manager password:

ns02.vns.local: replica
  last init status: None
  last init ended: 1970-01-01 00:00:00+00:00
  last update status: Error (-1) Problem connecting to replica - LDAP error: Can't contact LDAP server (connection error)
  last update ended: 1970-01-01 00:00:00+00:00
ns01.vns.local: replica
  last init status: None
  last init ended: 1970-01-01 00:00:00+00:00
  last update status: Error (-1) Problem connecting to replica - LDAP error: Can't contact LDAP server (connection error)
  last update ended: 1970-01-01 00:00:00+00:00


[root@ns03 ~]# telnet ns01.vns.local 389
Trying 172.31.35.249...
Connected to ns01.vns.local.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
[root@ns03 ~]# telnet ns02.vns.local 389
Trying 172.31.36.31...
Connected to ns02.vns.local.
Escape character is '^]'.
^]
telnet> quit
Connection closed.

[root@ns03 ~]# ipa-replica-manage force-sync --from ns01.vns.local
Directory Manager password:

ipa: ERROR: Unable to find replication agreement for ns03.vns.local
Unable to proceed

Haven't tried anything else at this point other than to take a backup of the VM.

Based on: https://www.freeipa.org/page/Backup_and_Restore We are thinking we can just promote ns03 to master and then removing all replication agreements, bring down ns01/02 and then reinitialize them using ns03 as the new master. Thoughts?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.