Hi Clément. After sync time in both servers I have many fewer cases with differences, but still appears some.
Today there was a password change that has modifyTimestamp Sep 23, 2014 6:58:56 PM ART (20140923215856Z) that 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)" attrs="uid objectClass javaSerializedData javaClassName javaFactory javaCodebase javaReferenceAddress javaClassNames javaremotelocation" [23/Sep/2014:18:59:02 -0300] conn=5357120 op=30060 SRCH base="ou=people,dc=xx,dc=com" scope=2 filter="(modifyTimestamp>=20140923215857Z)" attrs="uid objectClass javaSerializedData javaClassName javaFactory javaCodebase javaReferenceAddress javaClassNames javaremotelocation" This was the only case in a day ! root@ldapproda:/etc/init.d# java -version java version "1.6.0_32" OpenJDK Runtime Environment (IcedTea6 1.13.4) (6b32-1.13.4-4ubuntu0.14.04.1) OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode) Any idea or workaround ? Many thanks Norberto www.redklee.com.ar tel [+54] 11 5273 6342 cel [+54 9] 11 5055 9853 linkedin On Mon, Sep 22, 2014 at 12:54 PM, Clément OUDOT <[email protected]> wrote: > > > 2014-09-22 17:46 GMT+02:00 Norberto Altalef <[email protected]>: >> >> Hi Clément. Many thanks for your answer. >> >> >> >> >> What happen if I have an update (following the example log) at 13:47:05 >> >> Is it catched ? I think is out of scope of both filters. >> >> >> > >> > Indeed. Can you confirm that LSC is running on the same host that the >> > directory? Else, are you sure both hosts have the same time? >> > >> >> lsc is running in the destination host, and you are rigth the >> destination host was 4 sec ahead ! >> Now the filters using modifyTimestamp are correct to catch all the >> updates. >> >> Although this should not happen again, I think that will be better run >> lsc in the source host. Am I right? > > > > There is no problem to run it on a different host, it just requires NTP on > the two host to have clock sync. > >> >> >> > >> >> >> >> Event based ldap source service would be a best option? >> >> But 389ds unfortunately is not listed as supported. >> >> Since 389DS comes from Netscape DIrectory Server. Can I use it as >> >> <serverType> ? >> >> >> > >> > >> > You can try to use "SunDS", but we have a little issue with it, as is >> > does >> > not perform the full sync before starting on-the-fly modifications (see >> > http://tools.lsc-project.org/issues/597) >> > >> > >> Do you recommend to use asyncLdapSourceService ? >> What are the advantages and disadvantages? >> > > asyncLdapSourceService is real time, as it get events on the fly. But we > mainly support it for OpenLDAP. > > > > > Clément. _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
