2014-09-24 4:43 GMT+02:00 Norberto Altalef <[email protected]>:
> Hi Clément. Hi, > 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 ? > > No idea, it seems that there is a difference between the exact time LSC does the request, and the time used to compute modifyTimeStamp fitler. Maybe a bug on our side. Clément.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
