The replication agreements to the "unsync" master says that update has
started, so it looks like replication connection is active.
You need to check the access and error logs of bot sides and check if
tehre is replication traffic
On 08/24/2016 06:33 PM, bahan w wrote:
Hey guys.
I performed it :
###
# /usr/bin/repl-monitor.pl <http://repl-monitor.pl> -f /tmp/checkconf -s
Directory Server Replication Status (Version 1.1)
Time: Wed Aug 24 2016 18:16:50
Master: <MASTER OK>:389 ldap://<MASTER OK>:389/
Replica ID: 4
Replica Root: dc=<REALM>
Max CSN: 57bdc897000300040000 (08/24/2016 18:17:27 3 0)
Receiver: <MASTER UNSYNCHRONIZED>:389 ldap://<MASTER UNSYNCHRONIZED>:389/
Type: master
Time Lag: 0:00:00
Max CSN: 57bdc897000300040000 (08/24/2016 18:17:27 3 0)
Last Modify Time: 8/24/2016 18:16:50
Supplier: <MASTER OK>:389
Sent/Skipped: 179031 / 1037
Update Status: 0 Replica acquired successfully: Incremental update started
Update Started: 08/24/2016 18:16:50
Update Ended: n/a
Schedule: always in sync
SSL: SASL/GSSAPI
Master: <MASTER UNSYNCHRONIZED>:389 ldap://<MASTER UNSYNCHRONIZED>:389/
Replica ID: 3
Replica Root: dc=<REALM>
Max CSN: 57bdbda1000000030000 (08/24/2016 17:30:41)
Receiver: <MASTER OK>:389 ldap://<MASTER OK>:389/
Type: master
Time Lag: - 0:22:29
Max CSN: 57bdb85c000000030000 (08/24/2016 17:08:12)
Last Modify Time: 8/24/2016 17:07:34
Supplier: <MASTER UNSYNCHRONIZED>:389
Sent/Skipped: 3 / 9045345
Update Status: 0 Replica acquired successfully: Incremental update started
Update Started: 08/24/2016 18:16:50
Update Ended: n/a
Schedule: always in sync
SSL: SASL/GSSAPI
###
Do you see something strange in there ?
I have another environment where I have two replicated master and they
are OK.
And when I check the same command, the result is a little bit different :
###
Master: <MASTER 1 OK>:389 ldap://<MASTER 1 OK>:389/
Replica ID: 4
Replica Root: dc=<REALM>
Max CSN: 57bdc88d000300040000 (08/24/2016 18:17:17 3 0)
Receiver: <MASTER 2 OK>:389 ldap://<MASTER 2 OK>:389/
Type: master
Time Lag: 0:00:00
Max CSN: 57bdc88d000300040000 (08/24/2016 18:17:17 3 0)
Last Modify Time: 8/24/2016 18:16:00
Supplier: <MASTER 1 OK>:389
Sent/Skipped: 343515 / 0
Update Status: 0 Replica acquired successfully: Incremental update
succeeded
Update Started: 08/24/2016 18:15:59
Update Ended: 08/24/2016 18:16:08
Schedule: always in sync
SSL: SASL/GSSAPI
Master: <MASTER 2 OK>:389 ldap://<MASTER 2 OK>:389/
Replica ID: 3
Replica Root: dc=<REALM>
Max CSN: 57bdc887000800030000 (08/24/2016 18:17:11 8 0)
Receiver: <MASTER 1 OK>:389 ldap://<MASTER 1 OK>:389/
Type: master
Time Lag: - 390:51:38
Max CSN: 57a8500d000400030000 (08/08/2016 11:25:33 4 0)
Last Modify Time: 8/8/2016 11:24:28
Supplier: <MASTER 2 OK>:389
Sent/Skipped: 5 / 2596073
Update Status: 0 Replica acquired successfully: Incremental update
succeeded
Update Started: 08/24/2016 18:16:00
Update Ended: 08/24/2016 18:16:12
Schedule: always in sync
SSL: SASL/GSSAPI
###
Best regards.
Bahan
--
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric
Shander
--
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go to http://freeipa.org for more info on the project
