Hi,

Thanks for the reply.

Can you please help me in understanding the two updates that has come in the two new LDAP releases "slapd-bdb contextCSN updates from updatedn" & " slapd syncrepl contextCSN storing in subentry".

Can you please suggest what configurations are required to frequently change the contextCSN in slapd.conf so that my script can pick the latest one? I am also attaching the python script which I am using to check the sync status across mirrors?

Could you please assist?

Many Thanks.

Rahul Manchanda

GS Selfcare Platform Build Team

Tel: +91 02066018100 Extn: 6178 SMTP: rahul.manchanda@bt.com

Office: Sharda Center ,6th Floor Annex Off Karve Road, Erandwana ,Pune-04

-----Original Message----- From: Howard Chu [mailto:hyc@symas.com] Sent: Monday, May 10, 2010 6:32 PM To: Manchanda,RK,Rahul,DKE C Cc: quanah@zimbra.com; openldap-technical@openldap.org Subject: Re: OpenLDAP: contextCSN check across mirrors

rahul.manchanda@bt.com wrote:

Thanks for the reply.

"Added slapd syncrepl contextCSN storing in subentry (ITS#6373)". In this point what I can understand is that contextCSN will also get stored in suffix entries as well as to sub entries as well. Please correct if wrong.

That's wrong. Read the manpage and/or the ITS for the actual behavior.

I have some doubts if you can please help in making it more clear:

1. Can the contextCSN entry differ at the sub entry level if compared

with suffix(root) entry level?

It will only be in one place or the other, not both.

2. If this is the case then a check will be required to each and every

entry if the sync is there at the dn level across mirrors and scripts need to be modified so as to put a loop till all the entries has been checked in that particular LDAP tree. Please correct if wrong.

No.

3. how will the contextCSN entries will get changed. Does checkpoint

plays a role in changing the contextCSN value or not?

No.

4. provider will not change the contextCSN until the whole data get

synched

False.

but will consumer will still be able to do so. Is this still the

scenario in the new version?

I don't understand the question.

Many Thanks in advance!!

Rahul Manchanda

GS Selfcare Platform Build Team

Tel: +91 02066018100 Extn: 6178 SMTP: rahul.manchanda@bt.com

Office: Sharda Center ,6th Floor Annex Off Karve Road, Erandwana ,Pune-04

-----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: Friday, May 07, 2010 4:48 PM To: Manchanda,RK,Rahul,DKE C; openldap-technical@openldap.org Subject: RE: OpenLDAP: contextCSN check across mirrors

--On Friday, May 07, 2010 7:50 AM +0100 rahul.manchanda@bt.com wrote:

...

Hi,

It is 2.4.19.

Please update your servers to 2.4.22 and see if it still occurs. Numerous fixes have occurred since the 2.4.19 release. I've noted some specific ones below that are likely of interest.

OpenLDAP 2.4.20 Release (2009/11/27) Added slapd syncrepl contextCSN storing in subentry

(ITS#6373)

     Fixed slapd syncrepl deletes in MirrorMode (ITS#6368)
     Fixed slapd syncrepl to use correct SID (ITS#6367)
     Fixed slapo-syncprov checkpoint conversion (ITS#6370)
     Fixed slapo-syncprov deadlock (ITS#6335)
     Fixed slapo-syncprov memory leak (ITS#6376)
     Fixed slapo-syncprov out of order changes (ITS#6346)
     Fixed slapo-syncprov psearch with stale cookie (ITS#6397)

OpenLDAP 2.4.21 Release (2009/12/20) Fixed slapd syncrepl freeing tasks from queue (ITS#6413) Fixed slapd syncrepl parsing of tls defaults (ITS#6419) Fixed slapd syncrepl uninitialized variables (ITS#6425)

OpenLDAP 2.4.22 Release (2010/04/24) Fixed slapd-bdb contextCSN updates from updatedn (ITS#6469)

--Quanah

--

Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc

---

Zimbra :: the leader in open source messaging and collaboration