Custom Query (196 matches)
Results (88 - 90 of 196)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #169 | ezyang | wontfix | Failed LDAP replication due to busy replica should only warn when persistent | |
| Description |
Failed LDAP replication due to busy replica is an intermittent error and not a problem unless it persists. Thus, Nagios should not immediately warn about it. |
|||
| #173 | ezyang | invalid | Zephyr messages to ldap error log | |
| Description |
/var/log/dirsrv/slapd-scripts/errors often contains valuable information that will let you know before Nagios starts warning about replication problems. It should get zephyred out. |
|||
| #174 | ezyang | invalid | Nagios plugin to check for different generation ID error message | |
| Description |
Check for the error message: [23/Sep/2010:15:18:56 -0400] NSMMReplicationPlugin - agmt="cn="GSSAPI Replication to whole-enchilada.mit.edu"" (whole-enchilada:389): Replica has a different generation ID than the local data. which indicates something has gone wrong with replication. This message does not appear to be picked up by our existing MMR checks. Old text: In the nsds50ruv attribute, replication agreements record a "generation ID" which prevents two masters initialized from different sources from attempting to overwrite each other and cause a mess. Unfortunately, this safety mechanism also means that replication doesn't work, and furthermore, while this will result in a lot of spew to the LDAP error log, this won't show up in the usual status field. We should check that all of the replication generations on our servers are consistent. |
|||
