[Date Prev][Date Next]
Re: synrepl sends wrong rid cookie?
Marc Patermann <firstname.lastname@example.org> writes:
> on the provider server there are 3 databases glued together with one
> sync provider in the top level database:
> overlay glue
> overlay syncprov
> syncprov-checkpoint 100 10
> syncprov-sessionlog 100
> one consumer replicates two of the three database, each to a database,
> each database has its own synrepl statement with an own searchbase to
> get only the entries of this tree/database from the provider.
> Each database has its own rid: 401 and 402.
> When something changes in database 1 ou=humans, rid=401, the change is
> When something changes in database 2 ou=linux, rid=402, it is
> not. Only after a restart of the consumer changes apply.
> Now I saw this in the log:
> 1. change in ou=humans (rid=401)
> 2. change in ou=linux (rid=402)
> 3. change in ou=linux (rid=402)
> I get the rid=402 changes!
> Is this a configuration error on my side?
> Provider is 2.4.23, consumer is 2.4.20.
most likely an error on your side :-)
you didn't provide the relevant configuration examples so I have to
make a guess:
is there a syncprov parameter declared for database 2?
Dieter Klünter | Systemberatung
GPG Key ID:8EF7B6C6