Hello,
After a power blackout we have some trouble with synchronization
between 389ds and AD.
Here are some debugging messages:
[13/Oct/2015:09:34:39 +0300] NSMMReplicationPlugin - windows sync -
agmt="cn=ad.curs.pub.ro" (ad:636): State: start_backoff -> backoff
[13/Oct/2015:09:34:39 +0300] - acquire_replica, supplier RUV:
[13/Oct/2015:09:34:39 +0300] NSMMReplicationPlugin - supplier:
{replicageneration} 547f9354000000010000
[13/Oct/2015:09:34:39 +0300] NSMMReplicationPlugin - supplier:
{replica 1 ldap://ldap.curs.pub.ro:389} 547f9663000000010000
561ca5b8000000010000 561ca5b8
[13/Oct/2015:09:34:39 +0300] - acquire_replica, consumer RUV:
[13/Oct/2015:09:34:39 +0300] - acquire_replica, consumer RUV = null
[13/Oct/2015:09:34:39 +0300] - acquire_replica, supplier RUV is newer
[13/Oct/2015:09:34:39 +0300] NSMMReplicationPlugin - windows sync -
agmt="cn=ad.curs.pub.ro" (ad:636): Cancelling linger on the connection
[13/Oct/2015:09:34:39 +0300] - _csngen_adjust_local_time: gen state
before 561ca5fb0001:1444718075:0:0
[13/Oct/2015:09:34:39 +0300] - _csngen_adjust_local_time: gen state
after 561ca5ff0000:1444718079:0:0
[13/Oct/2015:09:34:39 +0300] NSMMReplicationPlugin - windows sync -
agmt="cn=ad.curs.pub.ro" (ad:636): State: backoff -> sending_updates
[13/Oct/2015:09:34:39 +0300] NSMMReplicationPlugin - windows sync -
agmt="cn=ad.curs.pub.ro" (ad:636): Replica has no update vector. It
has never been initialized.
[13/Oct/2015:09:34:39 +0300] NSMMReplicationPlugin - windows sync -
agmt="cn=ad.curs.pub.ro" (ad:636): Beginning linger on the connection
[13/Oct/2015:09:34:39 +0300] NSMMReplicationPlugin - windows sync -
agmt="cn=ad.curs.pub.ro" (ad:636): State: sending_updates ->
start_backoff
^C
What action should we take to solve this issue?
Thank you,
Mihai Carabas
Show replies by date