[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: replication on 2.1.5

To: Allan E Johannesen <aej@WPI.EDU>
Subject: Re: replication on 2.1.5
From: Matthew J Backes <lucca@csun.edu>
Date: Fri, 4 Oct 2002 09:37:04 -0700
Cc: openldap-software@OpenLDAP.org
In-reply-to: <15773.35080.128368.40629@ccc9.WPI.EDU>
Organization: California State University Northridge
References: <15773.35080.128368.40629@ccc9.WPI.EDU>

On Fri, 4 Oct 2002 08:26:48 -0400
Allan E Johannesen <aej@WPI.EDU> wrote:

> replace: entryCSN
> entryCSN: 2002100412:17:48Z#0x0001#0#0000

> in the midst of the changes.  The replication event is rejected with
> "constraint violation".

This happens because entryCSN is set to disallow user modification.
For some reason, your slave doesn't think it is a slave.

> The replication dn is in a group with write access to *.
> 
> Is that not good enough in 2.1.5?
> 
> I guess, in other words, what have I done wrong?

Check to make sure that the slave database is configured with an
updatedn line.

Even the rootdn cannot write to such attributes; only the configured
replication-update dn.

Matthew Backes
lucca@csun.edu

By the way, how's WPI doing?  Haven't been there since 1995...  does
the Wedge still exist?

References:
- replication on 2.1.5
  - From: Allan E Johannesen <aej@WPI.EDU>

Prev by Date: Re: Restrict Access to one value of multivalued Entry
Next by Date: Re: replication on 2.1.5
Index(es):
- Chronological
- Thread