1142152 – bind hangs after reload/GSSAPI Error: The referenced context has expired (Success)

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.

Bug 1142152 - bind hangs after reload/GSSAPI Error: The referenced context has expired (Success)

Summary: bind hangs after reload/GSSAPI Error: The referenced context has expired (Suc...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	bind
Sub Component:
Version:	6.6
Hardware:	Unspecified
OS:	Unspecified
Priority:	medium
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	Tomáš Hozza
QA Contact:	Tereza Cerna
Docs Contact:
URL:
Whiteboard:
Depends On:	1142150 1142176
Blocks:	1153398 1159820
TreeView+	depends on / blocked

Reported:	2014-09-16 09:12 UTC by Arpit Tolani
Modified:	2019-07-11 08:11 UTC (History)
CC List:	7 users (show)
Fixed In Version:	bind-9.8.2-0.32.rc1.el6
Doc Type:	Bug Fix
Doc Text:	BIND incorrectly handled errors returned by dynamic databases (from dyndbAPI). Consequently, BIND could enter a deadlock situation on shutdown under certain circumstances. The dyndb API has been fixed not to cause a deadlock during BIND shutdown after the dynamic database returns an error, and BIND now shuts down normally in the described situation.
Clone Of:	1142150
Environment:
Last Closed:	2015-07-22 05:50:11 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
SRPM with bind-dyndb-ldap plugin for testing of this bug (311.71 KB, application/x-rpm) 2014-12-09 08:35 UTC, Tomáš Hozza	no flags	Details
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2015:1250	0	normal	SHIPPED_LIVE	bind bug fix and enhancement update	2015-07-20 17:50:10 UTC

Description Arpit Tolani 2014-09-16 09:12:48 UTC

+++ This bug was initially created as a clone of Bug #1142150 +++

Description of problem:
bind hangs after reload/GSSAPI Error: The referenced context has expired (Success)

 After a while (about once in a week) the bind daemon is in the state hang/zombie. The bind daemon seems to be present and accept requests from the clients, but is not answering any dns requests. Only killing the process with kill -9 can stop the daemon. After starting bind again, it works fine, until the problem occurs again.

Version-Release number of selected component (if applicable):
bind-9.9.4-14.el7.x86_64

How reproducible:
Everytime Logrotates runs. 

Steps to Reproduce:
1. Configure IPA server with DNS
2. Wait till logrotate starts rotating. 

Additional info:
It is related to https://fedorahosted.org/bind-dyndb-ldap/ticket/131

Comment 1 Tomáš Hozza 2014-09-16 09:51:30 UTC

It is too late for 6.6. Moving to 6.7.

Comment 2 Petr Spacek 2014-09-16 17:29:37 UTC

There is nothing private in this bug. Publicizing.

Comment 3 Tomáš Hozza 2014-09-17 18:31:57 UTC

patch added to Bug #1142150

reproducer added in Bug #1142150 comment #7

Comment 5 Tomáš Hozza 2014-12-09 08:35:52 UTC

Created attachment 966145 [details]
SRPM with bind-dyndb-ldap plugin for testing of this bug

Comment 6 Tomáš Hozza 2014-12-09 09:35:01 UTC

Steps to reproduce for QA:

1. install bind
2. build the attachment 966145 [details] for your architecture
3. install the bind-dyndb-ldap package built from attachment 966145 [details]
4. Add the following section to /etc/named.conf:

dynamic-db "my_db_name" {
	library "ldap.so";
	arg "uri ldap://ldap.example.com";
	arg "base cn=dns, dc=example, dc=com";
	arg "auth_method none";
};

5. export KRB5_KTNAME=/etc/named.keytab
6. run 'named -u named -fg' as root
7. named will start
8. run 'rndc reload' from another console and watch the error on output:

[root@localhost ~]# rndc reload
rndc: 'reload' failed: out of memory

9. press CTRL+C in the terminal you've started named or run 'rndc halt'


Actual result in 9.:
Named will freeze and the only way to stop it is to kill -9 it.

Expected result in 9. (and with attached patch):
Named will exit just normally.

Comment 9 Tereza Cerna 2015-03-04 10:36:08 UTC

==================================
Verified in version:
    bind-9.8.2-0.36.rc1.el6.x86_64
PASSED
==================================

=== 1. console ===
# named -u named -fg
...
04-Mar-2015 11:25:15.231 running

=== 2. console ===
# rndc reload
server reload successful
# rndc halt
#

=== 1. console ===
04-Mar-2015 11:27:05.015 exiting
# echo $?
0

Named exited normally.

======================================
Reproduced in version:
    bind-9.8.2-0.30.rc1.el6_6.1.x86_64
FAIL
======================================

=== 1. console ===
# named -u named -fg
...
04-Mar-2015 11:14:31.432 running

=== 2. console ===
# rndc reload
rndc: 'reload' failed: out of memory
# rndc halt
#

=== 1. console ===

Named freezed.

Comment 11 errata-xmlrpc 2015-07-22 05:50:11 UTC

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.

https://rhn.redhat.com/errata/RHBA-2015-1250.html

Note You need to log in before you can comment on or make changes to this bug.