[Date Prev][Date Next]
Re: syncrepl replication on 2.4.19 (stable)
Brett @Google wrote:
> On Wed, Nov 4, 2009 at 5:48 PM, Brett @Google <firstname.lastname@example.org
> <mailto:email@example.com>> wrote:
> I am having a very odd problem after upgrading from openldap 2.4.16
> In the interests of full disclosure, I just did a slapcat / slapadd and
> the problem has gone away.
> I'm not sure is the problem was created because of starting a 2.4.19
> slapd, over the top of a database loaded by 2.4.16, or due to the
> obscure bug, occasionally mentioned, where syncrepl can gets itself into
> a odd state and wont converge.
> The syncrepl state information on the producer would have been created
> with the slapadd -w option under 2.4.16, but executed under 2.4.19. I
> thought originally because the berkeleydb version (4.8) had not changed,
> this would be ok.
> Out of interest, has the syncrepl UUID / CSN format changed much between
> 2.4.16 stable and 2.4.19 stable ?
There have been no format changes. You should have been able to run 2.4.19
directly on the original database. No idea what issue you ran into.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/