If connection with LDAP server cannot be established, it is not possible to shutdown BIND correctly. (Example situation: Admin made mistake in LDAP server URI or server network/LDAP server is not functional.)
Steps to reproduce: 1) Set uri parameter in /etc/named.conf to nonsense (ex. ldap://127.0.0.1:111) 2) run BIND (systemctl start named.service) 3) try to stop BIND via rndc stop or rndc halt
Result: BIND still runs.
Expected result: BIND was shutdown correctly.
BIND log: Server was shutdown, but psearch watcher still runs and holds named process. shutdown_psearch
Fixed by: https://fedorahosted.org/bind-dyndb-ldap/changeset/55d2886bb016adf3081a25eea616ce40f17d03e4
Code fixed to follow coding standard: https://fedorahosted.org/bind-dyndb-ldap/changeset/284ee38e4cb55766317822a6db0ac2a776435fa5
Metadata Update from @pspacek: - Issue assigned to pspacek - Issue set to the milestone: 0.1.1ipa
Log in to comment on this ticket.