Issue #729 has been updated by Clément OUDOT.

Target version changed from 2.1.2 to Not planned

We delay this issue cause we can't reproduce it for now. Your workaround is the 
best solution until we fix it.
----------------------------------------
Bug #729: fail to sync in async mode
http://tools.lsc-project.org/issues/729

Author: Norberto Altalef
Status: Assigned
Priority: Normal
Assigned to: Raphaël Ouazana
Category: Core
Target version: Not planned
Problem in version: 


I founded a difference between the exact time LSC does the request, and the 
time used to compute modifyTimeStamp filter in async mode.
The search interval is not always 5 sec, but the modifyTimeStamp keeps always 
in 5 sec before the request time.

In this condition some updates are not synced.

Example (389ds as source -> OpenLDAP as destination):

A password change with modifyTimestamp Sep 23,2014 6:58:56 PM ART 
(20140923215856Z) was no updated in the
destination server.

23/Sep/2014:18:58:56 -0300] conn=5357120 op=30052 SRCH
base="ou=people,dc=xx,dc=com" scope=2
filter="(modifyTimestamp>=20140923215852Z)" ....

[23/Sep/2014:18:59:02 -0300] conn=5357120 op=30060 SRCH
base="ou=people,dc=xx,dc=com" scope=2
filter="(modifyTimestamp>=20140923215857Z)" ....




-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://tools.lsc-project.org/my/account
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org

lsc-dev mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-dev

Reply via email to