LDAP Programming
 
Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
User Name:
Password:
Remember me
Go Back   Dev Shed ForumsDatabasesLDAP Programming

Reply
Add This Thread To:
  Del.icio.us   Digg   Google   Spurl   Blink   Furl   Simpy   Y! MyWeb 
Thread Tools Search this Thread Rate Thread Display Modes
 
Unread Dev Shed Forums Sponsor:
Stop making mediocre tutorials.The best tutorials are video! Camtasia Studio makes it easy to create engaging, buzz-building screen videos at any size, in any popular format. Download the free trial!
  #1  
Old May 5th, 2008, 05:24 AM
Armpstar Armpstar is offline
Registered User
Dev Shed Newbie (0 - 499 posts)
 
Join Date: May 2008
Posts: 1 Armpstar User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: 1 h 44 m 25 sec
Reputation Power: 0
Syncrepl multi-master

Dear All, I think I know very little about LDAP. Was struggling to configure it for the underlying configuration. Was just wondering if anyone could help me in this regard as I'm running out of time already.

I wanted to configure it for two LDAP masters (I mostly see 3 everywhere on web, I tried to correlate and implement for 2 but for no avail). May be I'm going wrong somewhere. As of now using a java stand alone program to write (can also be read is "create") records to one LDAP master (read Master 1). And use LDAP browser to verify the data being altered. I did try to configure it but luck didn't favor. My hunch was the data being modified in Master 1 should reflect to Master 2 in exact. But it doesn't seem to work, was puzzled where I might have gone wrong. Please someone also guide me on where/how can I see logs for the same in UNIX(learning to work on unix system) system if they can be helpful. Would be grateful if someone could really point out my mistake or in my very understanding. Thanking you in advance and awaiting a response. Here follow the details fyi,

###############################################################################################
# Master 1:
###############################################################################################
##
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#
include /usr/local/etc/openldap/schema/core.schema
include /usr/local/etc/openldap/schema/user.schema
include /usr/local/etc/openldap/schema/ticket.schema

# Define global ACLs to disable default read access.

# Do not enable referrals until AFTER you have a working directory
# service AND an understanding of referrals.

pidfile /usr/local/var/run/slapd.pid
argsfile /usr/local/var/run/slapd.args

# rootdn can always read and write EVERYTHING!
access to *
by self write
by * read

#######################################################################
# BDB database definitions
#######################################################################
database bdb
suffix "dc=example,dc=com"
rootdn "cn=root,dc=example,dc=com"

# Cleartext passwords, especially for the rootdn, should
# be avoid. See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
rootpw dirtysecret2

# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
directory /usr/local/var/openldap-data

# replication
#updatedn "dc=example, dc=com"

########################################################################
# Indexing
########################################################################
index entryCSN eq
index entryUUID eq
index objectClass eq

########################################################################
# enable a lot of logging - we might need it
########################################################################
loglevel -1

########################################################################
# Multi-Master Setup
########################################################################
syncRepl rid=001
provider=ldap://Master1:389
type=refreshAndPersist
retry="5 + 5 +"
searchbase="dc=example,dc=com"
attrs=*
interval=00:00:00:05
bindmethod=simple
binddn="cn=root,dc=example,dc=com"
credentials=dirtysecret1

#syncRepl rid=002
# provider=ldap://Master2:389
# type=refreshAndPersist
# retry="5 + 5 +"
# searchbase="dc=example,dc=com"
# anagerttrs=*
# interval=00:00:00:05
# bindmethod=simple
# binddn="cn=root,dc=example,dc=com"
# credentials=dirtysecret2

#########################################################################
# Provider to use the syncprov overlay
#########################################################################
overlay syncprov

#########################################################################
# contextCSN saved to database every 100 updates or ten minutes
#########################################################################
syncprov-checkpoint 100 10
syncprov-sessionlog 100

#########################################################################
mirrormode true
serverID 2
database monitor
#updateref ldap://Master2:389


###############################################################################################
# Master 2:
###############################################################################################
#
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#
include /usr/local/etc/openldap/schema/core.schema
include /usr/local/etc/openldap/schema/user.schema
include /usr/local/etc/openldap/schema/ticket.schema

# Define global ACLs to disable default read access.

# Do not enable referrals until AFTER you have a working directory
# service AND an understanding of referrals.

pidfile /usr/local/var/run/slapd.pid
argsfile /usr/local/var/run/slapd.args

# rootdn can always read and write EVERYTHING!
access to *
by self write
by * read

#######################################################################
# BDB database definitions
#######################################################################
database bdb
suffix "dc=example,dc=com"
rootdn "cn=root,dc=example,dc=com"

# Cleartext passwords, especially for the rootdn, should
# be avoid. See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
rootpw dirtysecret1

# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
directory /usr/local/var/openldap-data

# replication
#updatedn "dc=example, dc=com"

###########################################################################
# Indices to maintain
###########################################################################
index entryCSN eq
index entryUUID eq
index objectClass eq

###########################################################################
# enable a lot of logging - we might need it
###########################################################################
loglevel -1

#######################################################################
# Multi-Master Setup
#######################################################################
#syncRepl rid=001
# provider=ldap://Master1:389
# type=refreshAndPersist
# retry="5 + 5 +"
# searchbase="dc=example,dc=com"
# attrs=*
# interval=00:00:00:05
# bindmethod=simple
# binddn="cn=root,dc=example,dc=com"
# credentials=dirtysecret1

syncRepl rid=002
provider=ldap://Master2:389
type=refreshAndPersist
retry="5 + 5 +"
searchbase="dc=example,dc=com"
attrs=*
interval=00:00:00:05
bindmethod=simple
binddn="cn=Manager,dc=example,dc=com"
credentials=dirtysecret2

###########################################################################
# Provider to use the syncprov overlay
###########################################################################
overlay syncprov

###########################################################################
# contextCSN saved to database every 100 updates or ten minutes
###########################################################################
syncprov-checkpoint 100 10
syncprov-sessionlog 100

###########################################################################
mirrormode true
serverID 1
database monitor
#updateref ldap://Master1:389



Also if I'm done with this I would like to know what the server will understand by each term used here in slapd.conf. Kindly point me where I can find the anatomy of slapd.conf file if you know. Thanks again!

Reply With Quote
Reply

Viewing: Dev Shed ForumsDatabasesLDAP Programming > Syncrepl multi-master


Thread Tools  Search this Thread 
Search this Thread:

Advanced Search
Display Modes  Rate This Thread 
Rate This Thread:


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
View Your Warnings | New Posts | Latest News | Latest Threads | Shoutbox
Forum Jump

 Free IT White Papers!
 
Accelerating Trading Partner Performance
One in five. That's how many partner transactions have at least one error. That is an amazing statistic, particularly given the extraordinary leaps in innovation across the global supply chain during the past two decades. Download this white paper to learn more.

 
Competing on Analytics
This Tech Analysis is designed to help identify characteristics shared by analytics competitors, and includes information about 32 organizations that have made a commitment to quantitative, fact-based analysis.

 
Cost Effective Scaling with Virtualization and Coyote Point Systems
An overview of the industry trend toward virtualization, how server consolidation has increased the importance of application uptime and the steps being taken to integrate load balancing technology with virtualized servers.

 
Five Checkpoints to Implementing IP Telephony
Implementation planning for IP PBX software and IP telephony has become vital as businesses replace discontinued legacy PBX phone systems. This informative whitepaper outlines five "checkpoints" for any implementation plan that will help make IP communications a successful proposition.

 
Hosted Email Security: Staying Ahead of New Threats
In the last two years, email has become a fierce battleground between the nefarious forces of spam and malware, and the heroes of messaging protection. The spam volumes increased alarmingly every month, bringing clever new forms of phishing and virus propagation attacks.

 

Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
  
 





© 2003-2008 by Developer Shed. All rights reserved. DS Cluster 1 hosted by Hostway