ZCS Multi-Server Install Guide 7.2
ZCS Multi-Server Install Guide 7.2
Open Source Edition


Configuring LDAP Replication > Error Codes and Status Explanations

Error Codes and Status Explanations
The following monitoring error codes and status explanations are given with this feature:
The master server has no replica servers and is considered a standalone master server.
Could not execute StartTLS
The replica server requires StartTLS and fails.
The replica server becomes out of sync. Status indicates amount of time the replica server is behind the master server in w=weeks, d=days, h=hours, m=minutes, and s=seconds.
For example, ldap002.example.com is the master server, and ldap003.example.com and ldap004.example.com are replicas servers. The following screen-shot shows that replica server ldap003 is in sync with the master server, as indicated by the Code:0 and Status: In Sync, and replica server ldap004 is currently down, as indicated by Code: 4 and Status: Server down.
zimbra@ldap002.example.com
Replica: ldap://ldap003.example.com:389 Code: 0 Status: In Sync
Replica: ldap://ldap004.example.com:389 Code: 4 Status: Server down
If the replica server becomes out of sync with the master server, the status given indicates in a time format how far behind the master server it has become:
Replica: ldap://ldap003.example.com:389 Code: 0 Status: In Sync
Replica: ldap://ldap004.example.com:389 Code: 6 Status: 0w 0d 0h 14m 42s behind
 
 
 
Copyright © 2012 VMware Inc.