[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Replication Problem
--On Sunday, June 20, 2004 9:57 AM +0100 TM <offmct@yahoo.com> wrote:
I've been trying to setup an ldap slave using
openldap-2.1.30 but the slave doesn't seem to get
syncronized with the master.
This apparently happens when i try to modify a record
in master and slurpd tries to send the changes to the
slaves. Here is a debug i get from the slave's
"/usr/local/libexec/slapd -d4"::::::::::::::::::::::::
[root@cielo openldap]# /usr/local/libexec/slapd -d4
daemon_init: <null>
daemon: socket() failed errno=97 (Address family not
supported by protocol)
bdb_initialize: Sleepycat Software: Berkeley DB
4.2.52: (December 3, 2003)
bdb_db_init: Initializing BDB database
bdb_db_open: dc=rldp,dc=com
slapd starting
connection_get(9)
==> bdb_bind: dn:
cn=Replicator,dc=design1,dc=rldp,dc=com
send_ldap_result: err=49 matched="" text=""
connection_get(9)
err=49
49 decimal is 31 hex
According to ldap error codes:
LDAP_INVALID_CREDENTIALS 0x31 The supplied credential is
invalid.
binddn="cn=Replicator,dc=design1,dc=rldp,dc=com"
bindmethod=simple
credentials={SSHA}55uf5qYLY2w11Ce9GNpTBeVIcCAOtvhF
suffix "dc=rldp,dc=com"
rootdn
"cn=Replicator,dc=design1,dc=rldp,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 secret
rootpw {SSHA}55uf5qYLY2w11Ce9GNpTBeVIcCAOtvhF
updatedn "cn=Replicator,dc=design1,dc=rldp,dc=com"
Is there anything wrong with my config? Any
suggestions to solve the problem? I use
openldap-2.1.30 with bdb-4.2.52. I have copied the
master's db to the slaves db so i'm pretty sure that
they are similar. My ldap doesn't use TLS.
What is the entry in your database for
cn=replicator,dc=design,dc=rldp,dc=com look like?
--Quanah
--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html