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

Re: "best" way to check if OpenLDAP replication is working



I can attest to that.  :)

Reloading a server used to be required at least once a month or so before we updated from 2.3 to 2.4.23 openldap (5 servers, including the single master) due to being out of sync.

- chris

Chris Jacobs, Systems Administrator, Technology Services Group
Apollo Group | Apollo Marketing & Product Development | Aptimus, Inc.
2001 6th Ave | Ste 3200 | Seattle, WA 98121
phone: 206.839-8245 | cell: 206.601.3256 | Fax: 208.441.9661
email:  chris.jacobs@apollogrp.edu

----- Original Message -----
From: openldap-technical-bounces@OpenLDAP.org <openldap-technical-bounces@OpenLDAP.org>
To: phalenor@gmail.com <phalenor@gmail.com>
Cc: openldap-technical@openldap.org <openldap-technical@openldap.org>
Sent: Tue May 31 15:31:49 2011
Subject: Re: "best" way to check if OpenLDAP replication is working

> That's all our nagios check script does. If you're finding that there
> are still differences in the contents of the directory even when
> contextCSN matches, then there's likely something else going on. At
> least, I've never seen the situation you describe in our production
> openldap cluster.

I think that a lot of our replication woes are the result of running some pretty ancient versions of OpenLDAP.  I'm in the process right now of upgrading our LDAP infrastructure to use all new 2.4.25 installations (rather than the 2.3.43 version that's bundled with CentOS) and I'm thinking that a lot of our replication issues might vanish once that upgrade is complete.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tim Gustafson                                                tjg@soe.ucsc.edu
Baskin School of Engineering                                     831-459-5354
UC Santa Cruz                                         Baskin Engineering 317B
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-



This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.