I’m having a hell of a time figuring out how to fix this issue and have a deadline of a few hours on getting a slave joined to this domain. Replication is broken across all slaves from the master after upgrading to 4.4.
In the listener log, I turned debugging to 4 and I think it’s because of an incorrect bind user that is being used. (listener.log taken from Master Domain controller)
29.05.19 14:04:20.897 LISTENER ( WARN ) : Notifier/LDAP server is ucs-master.int.exampledomain.com:7389 29.05.19 14:04:20.897 LDAP ( PROCESS ) : connecting to ldap://ucs-master.int.exampledomain.com:7389 29.05.19 14:04:20.905 LDAP ( INFO ) : simple_bind as cn=admin,dc=int,dc=exampledomain,dc=com 29.05.19 14:04:20.907 LISTENER ( INFO ) : connecting to notifier ucs-master.int.exampledomain.com:6669 29.05.19 14:04:20.908 LISTENER ( INFO ) : connection to 10.5.35.10 failed with errorcode 111: Connection refused 29.05.19 14:04:20.908 LISTENER ( ERROR ) : failed to connect to any notifier 29.05.19 14:04:20.909 LISTENER ( WARN ) : can not connect any server, retrying in 30 seconds
In LDAP, the ‘cn=admin,dc=int,dc=exampledomain,dc=com’ DN does not exist. How do I resolve this issue?