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

Re: OpenLDAP Replication



By 'ADDRESS-OF-MASTER' I meant either the FQDN, or the IP address of the 
master server, not 'localhost'. 
'localhost' refers to ITSELF and on the slave server you're telling the 
slave server to use itself as a referral.

JM



Alex Franko <frankoalex@yahoo.com> 
10/22/2004 05:38 PM

To
jmorin@dominiondiagnostics.com
cc

Subject
Re: OpenLDAP Replication






That how it looks like:
in my SALPD.CONF  the
updateref   ldap://localhost:389
 
the localhost is the same what you mean ADDRESS-OF-MASTER.

updateref ldap://ADDRESS-OF-MASTER:389

jmorin@dominiondiagnostics.com wrote:
slapd.conf for replica should look like this ( I think)

SLAPD.CONF for Replica:
###############################
database bdb
suffix "o=myorg,c=US"
directory C:\\DATA\\Replica\\
rootdn cn=Mgr,o=myorg,c=US
rootpw secret
updatedn cn=Replica,o=myorg,c=US
updateref ldap://ADDRESS-OF-MASTER:389
##################################

Joe Morin




Alex Franko 
Sent by: owner-openldap-software@OpenLDAP.org
10/22/2004 04:55 PM

To
openldap-software@OpenLDAP.org
cc

Subject
OpenLDAP Replication






I'm relatively new in OpenLDAP and need your help to solve the problem
with OpenLDAP replication.

Here is my problem description:
I'm using openldap-2.1.30.
I'm trying to write to Replica(Slave) and I'm expecting that Replica will 
return referral
to Master. The Client (oldap32.lib) will automatically resend update 
request to the Master and Master will update its database, write the 
updates to the Replog file and SLURPD will bind to Replica and update 
Replicas database.
But this mechanism is broken at the beginning. The Client receives 
referral, and exits with the error message:

*****************************************
ldap_perror
ldap_add: Referral (10)
referrals:
ldap://localhost:389/o=myorg,c=US
ldap_unbind
ldap_free_request (origid 2, msgid 2)
ldap_free_connection
ldap_send_unbind;
...
*******************************************

SLAPD.CONF for Master:
###########################
database bdb
suffix "o=myorg,c=US"
rootdn "cn=Mgr,o=myorg,c=US"
rootpw secret
directory C:\\DATA\\Master
replogfile C:\\DATA\\Master\\slapd.replog
replica host=ldap://localhost:9010
binddn="cn=Replica,o=myorg,c=US"
bindmethod=simple
credentials=secret
###############################

SLAPD.CONF for Replica:
###############################
database bdb
suffix "o=myorg,c=US"
directory C:\\DATA\\Replica\\
rootdn cn=Mgr,o=myorg,c=US
rootpw secret
updatedn cn=Replica,o=myorg,c=US
updateref ldap://localhost:389
##################################

The commands that I'm running:

slapd -h ldap://localhost:389 - for Master
slapd -h ldap://localhost:9010 - for Replica

and
ldapmodify -a -x -h localhost:9010 -D "cn=Mgr,o=myorg,c=US" -w secret -f 
data.LDIF ;

Could you please help me?
May be I misunderstood the documentation and my expectation that Client 
should
automatically redirect request to the Master is wrong? 
Or may be someting wrong with my CONF files?

Thank you in advance,
Alex.





---------------------------------
Do you Yahoo!?
vote.yahoo.com - Register online to vote today!


CONFIDENTIALITY NOTICE: This e-mail, including attachments, is for the 
sole use of the individual to whom it is addressed. This message is 
confidential and may contain information that is privileged, confidential 
and is exempt from disclosure under applicable law. Any unauthorized 
review, use, disclosure or distribution is prohibited. If you have 
received this e-mail in error, please notify the sender by reply e-mail 
and destroy this message and its attachments.



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


CONFIDENTIALITY NOTICE: This e-mail, including attachments, is for the sole use of the individual to whom it is addressed. This message is confidential and may contain information that is privileged, confidential and is exempt from disclosure under applicable law. Any unauthorized review, use, disclosure or distribution is prohibited. If you have received this e-mail in error, please notify the sender by reply e-mail and destroy this message and its attachments.