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

Re: Syncrepl question

To: Ivan Ordonez <iordonez@nature.berkeley.edu>, openldap-technical <openldap-technical@openldap.org>
Subject: Re: Syncrepl question
From: Quanah Gibson-Mount <quanah@zimbra.com>
Date: Wed, 03 Dec 2008 18:00:24 -0800
Content-disposition: inline
In-reply-to: <49373762.1030403@nature.berkeley.edu>
References: <48B81CEB.7030503@nature.berkeley.edu> <200808291827.12177.bgmilne@staff.telkomsa.net> <48B82BA8.7010109@nature.berkeley.edu> <49373762.1030403@nature.berkeley.edu>

--On Wednesday, December 03, 2008 5:50 PM -0800 Ivan Ordonez <iordonez@nature.berkeley.edu> wrote:

I still can't get syncrepl to work on our machines.

Looking at the log, the one error that stands out to me is the error
below.  I get this error when I start LDAP.

slapd[16146]: do_syncrep1: rid 001 ldap_sasl_bind_s failed (13)
slapd[16146]: do_syncrepl: rid 001 quitting

I'm not sure why it is failing since I know for sure, my password is
correct.  Removing the "updatedn" line will get rid of the error, but
that doesn't fix the issue.  Any changes I made on the Master server
doesn't replicate or go to the Slave server.


updatedn is not valid for a syncrepl statement.

--Quanah

--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration

References:
- Re: Syncrepl question
  - From: Ivan Ordonez <iordonez@nature.berkeley.edu>

Prev by Date: Re: Syncrepl question
Next by Date: Re: Syncrepl question
Index(es):
- Chronological
- Thread