Unable to bind to master (zmreplchk)

=Unable to bind to master (zmreplchk)

 - This article is a Work in Progress, and may be unfinished or missing sections.

Unable to bind to master (zmreplchk)

 - This article is a Work in Progress, and may be unfinished or missing sections.

Resolution

To fix the error, we need to check the ldap passwords set on the second master that was installed with the following command:

$ zmlocalconfig -s | grep -i pass

And the output will be similar to:

antispam_mysql_password =
antispam_mysql_root_password =
client_ssl_truststore_password = ${mailboxd_truststore_password}
crocodoc_password = H4aI35Y2n517oCh
imapd_keystore_password = ${mailboxd_keystore_password}
ldap_amavis_password = SMZwo0sX5P
ldap_bes_searcher_password = SMZwo0sX5P
ldap_nginx_password = 3kS_wLCC9
ldap_postfix_password = SMZwo0sX5P
ldap_replication_password = 3kS_wLCC9
ldap_root_password = SMZwo0sX5P
mailboxd_keystore_base_password = zimbra
mailboxd_keystore_password = hGl_o47dJ
mailboxd_truststore_password = changeit
mysql_root_password = 95F_.n_C4PPm9zl_eJTFb_Dsv
smime_truststore_password = ${mailboxd_truststore_password}
zimbra_ldap_password = 3kS_wLCC9
zimbra_mysql_password = 5v.l7a2LnJNlytUnfSYGmI3TkpUtBgC7
zimbra_vami_password = vmware

From the output above, in bold font, we see some of the passwords are different than the ones set on the master (3kS_wLCC9). To fix the issue, we need to make sure that they match:

$ zmldappasswd -r 3kS_wLCC9
Updating local config and LDAP
$ zmldappasswd -p 3kS_wLCC9
Updating local config and LDAP
$ zmldappasswd -a 3kS_wLCC9
Updating local config and LDAP
$ zmldappasswd -b 3kS_wLCC9
Updating local config and LDAP

$ ldap stop;ldap start
Killing slapd with pid 6213 done.
Started slapd: pid 14653

Once the passwords are set and ldap restarted, we check again:

$ /opt/zimbra/libexec/zmreplchk
Master: ldap://test.azmo.com:389 ServerID: 2 Code: 0 Status: In Sync CSNs:
20181202040009.206786Z#000000#001#000000
20181202034620.334844Z#000000#002#000000
Master: ldap://seven.azmo.com:389 ServerID: 1 Code: 0 Status: In Sync CSNs:
20181202040009.206786Z#000000#001#000000
20181202034620.334844Z#000000#002#000000

After the passwords are fixed on the second Master, the same command will work on the first Master as well.