Re: Monitor the SyncRepl replication status

[Buchan Milne <bgmilne@staff.telkomsa.net>]

On Wednesday 05 September 2007 14:14:56 Aaron Richton wrote:
> http://www.openldap.org/lists/openldap-software/200602/msg00158.html
>
> We use this with only slight modifications. Of course, the only time it
> has ever produced a meaningful notification has been for a few minutes
> following a fresh server install as changes made since the last slapcat
> replicate in. (And since that's an expected condition, it's of minimal
> interest to me on Nagios.)
>
> I'll note that all of our syncrepl failures (which are zero as of late;
> run 2.3.38!) were much more insidious bugs that updated contextCSN because
> "they thought they worked."
>
> On Wed, 5 Sep 2007, Bruno Lezoray EMSM wrote:
> > Hi all,
> >
> > few months ago, i developed script to monitor slurpd replication, by
> > checking replication logs.
> > Now, we want to implement SyncRepl replication, and it looks more
> > complex to know a status of the replication.
> > Is someone already developed a tool  to do that ?
> >
> > My first idea is to compare the contextCSN of the suffix entry between
> > the master and the slave.
> > I don't know if there is some specific logs that indicate the
> > replication is broken.



Here is mine, which I use with Hobbit, but which can also be used standalone 
(with name/IP of servers as arguments):

http://staff.telkomsa.net/~bgmilne/bb-openldap.pl

It also does performance monitoring (e.g. graphs of searches, binds, 
operations etc.) in conjunction with Hobbit. It needs no configuration (finds 
all databases with syncrepl, and the updateref for the database, from the 
contents of the monitor backend), but requires (at present) anonymous access 
to cn=monitor.

What it does pick up for me is when replication is interrupted on servers 
separated by a firewall (which I have started observing again, now that we do 
actually have some slaves on a different network).


Regards,
Buchan