Re: syncrepl replication on 2.4.19 (stable)

"Brett @Google" <[email protected]>
Newsgroups gmane.network.openldap.general
Message-ID <[email protected]>
On Thu, Nov 5, 2009 at 4:20 AM, Howard Chu <[email protected]> wrote:

>
> > 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.
>

The problem came back, but I think i found the root cause. We have a batch
script which starts slapd, it has always been the same on both the producers
and consumers. The "-w" slapadd option was being provided in this script,
for both the consumer and the producer. This has been the case for quite
some time (2.3.x and 2.4.16), but it only recently became an issue after the
upgrade to 2.4.19. The sync problem would then appear or disappear randomly,
depending of which of the provider or consumer was loaded first.

Is it patently wrong to provide the "-w" option on the consumer, or is this
a bug ?

At the very least it is probably a usability "gotcha", if not a bug.

If this is an issue perhaps slapadd should refuse to do "-w" on a shadow
context, or warn and not actually perform the option ?

Cheers
Brett
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.