[Date Prev][Date Next]
RE: Constraint violation in Replication setup.
- To: "Quanah Gibson-Mount" <firstname.lastname@example.org>, <OpenLDAP-software@OpenLDAP.org>
- Subject: RE: Constraint violation in Replication setup.
- From: "Reinhard Nappert" <email@example.com>
- Date: Mon, 7 Mar 2005 14:28:00 -0500
- Content-class: urn:content-classes:message
- Thread-index: AcUjSrBYa8vYFDmkSVCzUSJDqeuoAgAAGmGA
- Thread-topic: Constraint violation in Replication setup.
It works now. My JNDI client does update the replicated environment. It
understands the referral and follows it. I meant that I should see
traffic between the master and the slave, performing the actual update.
Did you experience replication hick-ups, depending on the location of
the replication directives in the slapd.conf file?
I noticed for example that the database monitor setting and the indexes
have to be configured after the replication section.
[mailto:owner-openldap-software@OpenLDAP.org] On Behalf Of Quanah
Sent: Monday, March 07, 2005 11:56 AM
Subject: RE: Constraint violation in Replication setup.
--On Monday, March 07, 2005 8:40 AM -0500 Reinhard Nappert
> You are right and my wording was misunderstanding. However, you still
> should see traffic from the master to the slave, which is not
> I also don't see any traffic from the client to the master. All that
> said, it seems that the referral part does not work.
> Does anyone see the reason, why it does not work.
I don't see why you think there would be any traffic between the slave
and the master when using a referral. As for the client and the master,
I'd guess that JNDI doesn't implement referrals correctly.
Principal Software Developer
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
"These censorship operations against schools and libraries are stronger
than ever in the present religio-political climate. They often focus on
fantasy and sf books, which foster that deadly enemy to bigotry and
blind faith, the imagination." -- Ursula K. Le Guin