Closed
Bug 1117439
Opened 9 years ago
Closed 9 years ago
Zimbra LDAP Replication on zmldap1.mail.pek1.mozilla.com is CRITICAL: CRITICAL: Replica: ldap://zmldap1.mail.pek1.mozilla.com:389 Code: 6 Status: 0y 0M 0w 0d 0h 6m 12s behind CSNs:
Categories
(Infrastructure & Operations :: MOC: Problems, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nagiosapi, Unassigned)
References
()
Details
(Whiteboard: [id=nagios1.private.pek1.mozilla.com:84768])
Automated alert report from nagios1.private.pek1.mozilla.com: Hostname: zmldap1.mail.pek1.mozilla.com Service: Zimbra LDAP Replication State: CRITICAL Output: CRITICAL: Replica: ldap://zmldap1.mail.pek1.mozilla.com:389 Code: 6 Status: 0y 0M 0w 0d 0h 6m 12s behind CSNs: Runbook: http://m.allizom.org/Zimbra+LDAP+Replication
Reporter | ||
Comment 1•9 years ago
|
||
Automated alert recovery: Hostname: zmldap1.mail.pek1.mozilla.com Service: Zimbra LDAP Replication State: OK Output: OK: Replica: ldap://zmldap1.mail.pek1.mozilla.com:389 Code: 0 Status: In Sync CSNs:
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•8 years ago
|
Component: MOC: Incidents → MOC: Problems
You need to log in
before you can comment on or make changes to this bug.
Description
•