Issue #729 has been updated by Norberto Altalef.
Hi. I think you may be rigth. The log system in 389ds has some type of buffering mechanism, since a tail -f on log file is not showing lines in real time. But ... the problem is that I have some missing updates. An average of one missing update every two days in a working environment of 6000 users. Taking one example. An entry with modifyTimestamp=Dec 17, 2014 11:39:28 AM ART (20141217143928Z), was not synced. This is the log around this time: [17/Dec/2014:11:39:16 -0300] filter="(modifyTimestamp>=20141217143911Z)" [17/Dec/2014:11:39:22 -0300] filter="(modifyTimestamp>=20141217143917Z)" [17/Dec/2014:11:39:28 -0300] filter="(modifyTimestamp>=20141217143922Z)" [17/Dec/2014:11:39:28 -0300] filter="(modifyTimestamp>=20141217143928Z)" [17/Dec/2014:11:39:29 -0300] filter="(modifyTimestamp>=20141217143929Z)" [17/Dec/2014:11:39:34 -0300] filter="(modifyTimestamp>=20141217143929Z)" As a temporal workaround I'm running a cron job with "lsc -s UserTask" each 10 min. ---------------------------------------- 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: 2.1.2 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
