Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 569371[details]
Server was shutdown, but psearch watcher still runs and holds named process.
Description of problem:
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.)
Version-Release number of selected component (if applicable):
bind-dyndb-ldap-1.1.0-0.3.b1.el6
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
Actual results:
BIND still runs.
Expected results:
BIND was shutdown correctly.
Additional info:
Upstream ticket: https://fedorahosted.org/bind-dyndb-ldap/ticket/55
Fixed in upstream: https://fedorahosted.org/bind-dyndb-ldap/changeset/55d2886bb016adf3081a25eea616ce40f17d03e4
Verified using:
ipa-server-3.0.0-19.el6.x86_64
bind-dyndb-ldap-2.3-1.el6.x86_64
Steps taken to verify:
# grep psearch /etc/named.conf
arg "psearch yes";
# service named status
version: 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6
CPUs found: 2
worker threads: 2
number of zones: 21
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (pid 11954) is running...
# vim /etc/named.conf
=> Updated line to be:
#arg "uri ldapi://%2fvar%2frun%2fslapd-TESTRELM-COM.socket";
arg "uri ldapi://127.0.0.1:111";
# service named restart
Stopping named: .[ OK ]
Starting named: [ OK ]
# pgrep named
23762
# rndc -V stop
create memory context
create socket manager
create task manager
create task
create logging context
setting log tag
creating log channel
enabling log channel
create parser
get key
decode base64 secret
stop
post event
using server 127.0.0.1 (127.0.0.1#953)
create socket
bind socket
connect
create message
render message
schedule recv
send message
parse message
create message
render message
schedule recv
send message
parse message
# service named status
rndc: connect failed: 127.0.0.1#953: connection refused
named dead but subsys locked
[root@ipaqa64vma ~]# pgrep named
[root@ipaqa64vma ~]#
Verified that BIND was shutdown correctly.
edited /etc/named.conf to go back to original line, and restarted named sucessfully after the test above.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0359.html