2009/2/16 jakjr joao.alfredo@gmail.com
sessionlog is a log of changes in-memory. But refreshAndPersist should replicate changes on fly.
So, to me, don't make any sense to keep this two options together.
Regards, Jakjr
Hello,
Yesterday, I went into 2.4.14. But I still have a problem contextcsn who is out of date. The 2 servers are synchronized via ntpdate but removing 2 values in a dc whith master1, l'entryCSN is correct:
master1:
dn: uid=XXXX,ou=utilisateurs,dc=glon,dc=com entryCSN: 20090218081359.232700Z#000000#001#000000
master2:
dn: uid=XXXXX,ou=utilisateurs,dc=glon,dc=com entryCSN: 20090218081359.232700Z#000000#001#000000
############
master1:
dn: cn=XXXX,ou=utilisateurs,dc=glon,dc=com entryCSN: 20090218083153.439947Z#000000#001#000000
dn: cn=XXXX,ou=utilisateurs,dc=glon,dc=com givenName: Test sn: TEST gidNumber: 1000 objectClass: inetOrgPerson objectClass: posixAccount objectClass: top homeDirectory: /home/users/test structuralObjectClass: inetOrgPerson creatorsName: cn=admin,dc=glon,dc=com cn: XXXXXXXXX userPassword:: e1NIQX1xVXFQNWN5eG02WWNUQWh6MDVIcGg1Z3Z1OU09 entryUUID: 05c2503e-9091-102d-805e-45c22a025713 createTimestamp: 20090216161716Z uid: test uidNumber: 1008 departmentNumber: 75 entryCSN: 20090218083153.439947Z#000000#001#000000 modifiersName: cn=admin,dc=glon,dc=com modifyTimestamp: 20090218083153Z
-----------------------------------------
master2:
dn: cn=XXXX,ou=utilisateurs,dc=glon,dc=com entryCSN: 20090218083153.439947Z#000000#001#000000
dn: cn=XXXX,ou=utilisateurs,dc=glon,dc=com givenName: Test sn: TEST gidNumber: 1000 objectClass: inetOrgPerson objectClass: posixAccount objectClass: top homeDirectory: /home/users/test structuralObjectClass: inetOrgPerson creatorsName: cn=admin,dc=glon,dc=com cn: XXXXXXXXXX userPassword:: e1NIQX1xVXFQNWN5eG02WWNUQWh6MDVIcGg1Z3Z1OU09 entryUUID: 05c2503e-9091-102d-805e-45c22a025713 createTimestamp: 20090216161716Z uid: test uidNumber: 1008 departmentNumber: 75 entryCSN: 20090218083153.439947Z#000000#001#000000 modifiersName: cn=admin,dc=glon,dc=com modifyTimestamp: 20090218083153Z
#############
but contextCSN: -----------------
Master1:
dn: dc=glon,dc=com contextCSN: 20090218083153.439947Z#000000#001#000000 contextCSN: 20090217135202.777737Z#000000#002#000000
Master2:
dn: dc=glon,dc=com contextCSN: 20090218081351.574766Z#000000#001#000000 contextCSN: 20090217135202.777737Z#000000#002#000000
[-------------]
With a change of master2:
Master1:
dn: dc=glon,dc=com contextCSN: 20090218081351.574766Z#000000#001#000000 contextCSN: 20090218085423.012016Z#000000#002#000000
Master2:
dn: dc=glon,dc=com contextCSN: 20090218083153.439947Z#000000#001#000000 contextCSN: 20090217135202.777737Z#000000#002#000000
by against, I can not understand the hours used.
master1:~# date Wed Feb 18 09:39:00 CET 2009
master2:~# date Wed Feb 18 09:39:02 CET 2009 I must have a delay of 2 seconds, yet the same ntp server.
Why contextcsn and entryCSN have values out of sync with the clock? 20090218081351 => 2009/02/18 à 08h13 51 s.
------- Guillaume.