Closed Bug 1117431 Opened 11 years ago Closed 11 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 5m 47s behind CSNs:

Categories

(Infrastructure & Operations :: MOC: Problems, task)

Product:
Infrastructure & Operations
Component:
MOC: Problems
Platform:
Other
Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nagiosapi, Unassigned)

References

(
URL
)

Details

(Whiteboard: [id=nagios1.private.pek1.mozilla.com:84723])

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 5m 47s behind CSNs: Runbook: http://m.allizom.org/Zimbra+LDAP+Replication
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: 11 years ago
Resolution: --- → FIXED
Component: MOC: Incidents → MOC: Problems
You need to log in before you can comment on or make changes to this bug.