Yes. I'm on my Master server. What's interesting though is that if I go to my 
slave server and stop ldap I can then write to my master. Is there someway that 
I could be talking to my slave when I run ldapadd from my master?


-Mike

> Date: Fri, 18 Feb 2011 09:53:24 +0100
> From: [email protected]
> To: [email protected]
> Subject: Re: Syncrepl in openldap 2.3.43
> CC: [email protected]
> 
> Michael,
> 
> Michael Starling schrieb am 18.02.2011 03:36 Uhr:
> > 
> > I've been using slurpd for quite some time now with fairly good results 
> > however I wanted to take advantage of the newer features in syncrepl. 
> > Specifically the ability to have the slave push to the master.
> > 
> > I was able to set this up in relative short order using the example 
> > provided in http://www.openldap.org/doc/admin23/syncrepl.html
> > 
> > I start up my slave server and it does indeed grab all the database 
> > information from my master, however I can no longer write to my master 
> > server. What am i missing from the documentation?
> > 
> > 
> > If I try to add a simple ldif file it fails with the following error:
> > 
> > [root@myserver backups]# ldapadd -f replicator-policy.ldif -x -D 
> > cn=root,dc=somedomain,dc=somedomain -W
> > Enter LDAP Password:
> > adding new entry "cn=replicate,ou=policies,dc=somedomain,dc=somedomain"
> > ldapadd: Server is unwilling to perform (53)
> >         additional info: shadow context; no update referral
> > 
> > If I add an updateref to my slave slapd.conf pointing back to my master 
> > server the error changes to this:
> > 
> > [root@myserver backups]# ldapadd -f replicator-policy.ldif -x -D 
> > cn=root,dc=somedomain,dc=somedomain -W
> > Enter LDAP Password:
> > adding new entry "cn=replicate,ou=policies,dc=somedomain,dc=somedomain"
> > ldapadd: Referral (10)
> >         referrals:
> >                 
> > ldap://myserver.aa.bb.cc:389/cn=replicate,ou=policies,dc=somedomain,dc=somedomain
> Are you really sure, you are talking to the master and not to the slave 
> instead?
> 
> Marc
                                          

Reply via email to