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

RE: Constraint violation in Replication setup.

Hi, again

It looks like the place where you put the replication definition is
quite important. After I placed them before the index definition
section, it worked. I also noticed that the "database monitor" directive
must be placed after the replication definition section.

Thanks for all your help

-----Original Message-----
From: owner-openldap-software@OpenLDAP.org
[mailto:owner-openldap-software@OpenLDAP.org] On Behalf Of Reinhard
Sent: Monday, March 07, 2005 8:41 AM
To: Quanah Gibson-Mount; OpenLDAP-software@OpenLDAP.org
Subject: RE: Constraint violation in Replication setup.

You are right and my wording was misunderstanding. However, you still
should see traffic from the master to the slave, which is not happening.
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.


-----Original Message-----
From: Quanah Gibson-Mount [mailto:quanah@stanford.edu]
Sent: Friday, March 04, 2005 5:34 PM
To: Reinhard Nappert; OpenLDAP-software@OpenLDAP.org
Subject: RE: Constraint violation in Replication setup.

--On Friday, March 04, 2005 2:53 PM -0500 Reinhard Nappert
<rnappert@juniper.net> wrote:

> Quanah, you might be right. I used just ldapBrowser for that initial 
> test.
> I wrote quickly a JNDI client, where I add the property to follow
> referrals:
> DirContext ctx = new InitialDirContext(env); 
> ctx.addToEnvironment(Context.REFERRAL,"follow");
> ....
> I still get the same error:
> javax.naming.NamingException: [LDAP: error code 80 - no 
> structuralObjectClass operational attribute]; remaining name 
> 'o=test,dc=net'
> I also snooped on port 389 and I do not see any traffic from the slave

> to the master. Somehow, it is not following the referral. The 
> updateref directive looks fine to me. Do you see any abnormal
configuration items.


I think you misunderstand referrals.  They work this way:

Client tries to make a modification to the slave.
Slave rejects the modification and returns the referral for the master
to the client.
The client then makes a new connection to the master, and updates the

So you should never see traffic from the slave to the master in this


Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
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