I just realized a better question might be: is it safe to grep out the
following line from the replication status results?
nsds5replicaLastUpdateStatus: 1 Can't acquire busy replica
Or can that error message occur in a situation where the replica somehow stays
permanently busy, and hence failed
Thanks for that. I had looked into that but it was a bit heavyweight compared
to what we are trying to do. I was hoping there was an easy way to simply have
the command-line ignore the condition where the servers were temporarily busy.
We are using AWS and having CloudWatch store statistics an
Hi,
we use http://cnmonitor.sourceforge.net/ to keep an eye on our ldap
servers, including replication.
Works nicely and sends mail if something goes amiss.
Mit freundlichen Grüßen,
Alexander Jung
2015-08-21 4:35 GMT+02:00 Russell Beall :
> Hello,
>
> I have deployed a MMR cluster with a rece
Hello,
I have deployed a MMR cluster with a recent (about April) version of 389 from
the CentOS 6 repository.
Following example 2 of this document, I have tried to set up a monitoring
script on each node to verify that replication is correctly succeeding:
http://directory.fedoraproject.org/docs
