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 1165796 - bind-dyndb-ldap crashes if server is shutting down and connection to LDAP is down
Summary: bind-dyndb-ldap crashes if server is shutting down and connection to LDAP is ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: bind-dyndb-ldap
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Tomas Krizek
QA Contact: Scott Poore
URL:
Whiteboard:
Depends On:
Blocks: 1205796 1298243
TreeView+ depends on / blocked
 
Reported: 2014-11-19 17:52 UTC by Scott Poore
Modified: 2019-03-22 07:25 UTC (History)
2 users (show)

Fixed In Version: bind-dyndb-ldap-11.1-1.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-08-01 19:27:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
named abrt email (94.33 KB, text/plain)
2014-11-19 17:53 UTC, Scott Poore 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2120 0 normal SHIPPED_LIVE bind-dyndb-ldap bug fix update 2017-08-01 18:15:06 UTC

Description Scott Poore 2014-11-19 17:52:57 UTC 
Description of problem:

While upgrading IPA servers from RHEL7.0 to 7.1, I'm seeing named crashes.

abrt_version:   2.1.11
backtrace_rating: 4
cmdline:        /usr/sbin/named -u named
crash_function: assertion_failed
executable:     /usr/sbin/named
hostname:       qe-blade-13.testrelm.test
kernel:         3.10.0-123.el7.x86_64
last_occurrence: 1416415625
pid:            13292
pkg_arch:       x86_64
pkg_epoch:      32
pkg_name:       bind
pkg_release:    14.el7
pkg_version:    9.9.4
pwd:            /var/named
runlevel:       N 3
time:           Wed 19 Nov 2014 11:47:05 AM EST
uid:            25
username:       named

I'll attach the full abrt shortly.

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


How reproducible:
always.

Steps to Reproduce:
1.  install IPA server on RHEL7.0
2.  add repo configs for RHEL7.1
3.  yum -y update 'ipa*' sssd

Actual results:
upgrade seems to work from shell but, named crashes.

Expected results:
no crash

Additional info:

I see messages like this in backtrace: 

:warning: .dynamic section for "/lib64/libgssapi_krb5.so.2" is not at the expected address (wrong library or version mismatch?)

I also see messages like this in /var/log/messages:

:Nov 19 11:47:39 qe-blade-13.testrelm.test named[7689]: validating @0x7f4e800008c0: . NS: got insecure response; parent indicates it should be secure
:Nov 19 11:47:39 qe-blade-13.testrelm.test named[7689]: error (insecurity proof failed) resolving './NS/IN': IP-ADDRESS-SCRUBBED#53
:Nov 19 11:47:39 qe-blade-13.testrelm.test named[7689]: validating @0x7f4e800008c0: . DNSKEY: got insecure response; parent indicates it should be
secure
:Nov 19 11:47:39 qe-blade-13.testrelm.test named[7689]: error (insecurity proof failed) resolving './DNSKEY/IN': IP-ADDRESS-SCRUBBED#53
:Nov 19 11:47:39 qe-blade-13.testrelm.test named[7689]: checkhints: unable to get root NS rrset from cache: not found

I'll attach full abrt email separately.
Comment 1 Scott Poore 2014-11-19 17:53:22 UTC 
Created attachment 959104 [details]
named abrt email
Comment 3 Petr Spacek 2014-11-25 19:02:18 UTC 
This is a harmless bug in bind-dyndb-ldap error handling. It can crash during shutdown if something is wrong with LDAP connection but the daemon is shutting down anyway so it should not cause any huge problem.

It seems that it affects all versions from at least 2011.


Most important part of the log is:

Nov 25 10:20:56 kvm-guest-01 ns-slapd: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (No Kerberos credentials available)
Nov 25 10:20:57 kvm-guest-01 systemd: Stopping Berkeley Internet Name Domain (DNS)...
Nov 25 10:20:57 kvm-guest-01 named[4805]: received control channel command 'stop'
Nov 25 10:20:57 kvm-guest-01 named[4805]: shutting down: flushing changes
Nov 25 10:20:57 kvm-guest-01 named[4805]: stopping command channel on 127.0.0.1#953
Nov 25 10:20:57 kvm-guest-01 named[4805]: stopping command channel on ::1#953
Nov 25 10:20:57 kvm-guest-01 named[4805]: ldap_helper.c:644: REQUIRE(pthread_kill(ldap_inst->watcher, 10) == 0) failed, back trace
Nov 25 10:20:57 kvm-guest-01 named[4805]: #0 0x7fba3d78e380 in ??
Nov 25 10:20:57 kvm-guest-01 named[4805]: #1 0x7fba3b9801ca in ??
Nov 25 10:20:57 kvm-guest-01 named[4805]: #2 0x7fba36f33cdd in ??
Nov 25 10:20:57 kvm-guest-01 named[4805]: #3 0x7fba36f3c591 in ??
Nov 25 10:20:57 kvm-guest-01 named[4805]: #4 0x7fba36f3c6aa in ??
Nov 25 10:20:57 kvm-guest-01 named[4805]: #5 0x7fba3cfb1659 in ??
Nov 25 10:20:57 kvm-guest-01 named[4805]: #6 0x7fba3d7a499b in ??
Nov 25 10:20:57 kvm-guest-01 named[4805]: #7 0x7fba3b9a28a6 in ??
Nov 25 10:20:57 kvm-guest-01 named[4805]: #8 0x7fba3b557df3 in ??
Nov 25 10:20:57 kvm-guest-01 named[4805]: #9 0x7fba3a8003dd in ??
Nov 25 10:20:57 kvm-guest-01 named[4805]: exiting (due to assertion failure)
Comment 4 Scott Poore 2014-11-25 19:07:21 UTC 
As far as I know, this is not currently causing a problem.  I think we could certainly move this out to 7.2.
Comment 5 Petr Spacek 2014-12-09 09:55:41 UTC 
Upstream ticket:
https://fedorahosted.org/bind-dyndb-ldap/ticket/149
Comment 12 Tomas Krizek 2017-02-08 16:24:48 UTC 
Fixed upstream

master:

https://git.fedorahosted.org/cgit/bind-dyndb-ldap.git/commit/?id=edd8c0552eb7e977a961c9492eb18c177685e438
Comment 13 Fedora Update System 2017-03-10 16:10:31 UTC 
bind-dyndb-ldap-11.1-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-56aa9caed6
Comment 14 Fedora Update System 2017-03-11 00:22:32 UTC 
bind-dyndb-ldap-11.1-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-56aa9caed6
Comment 15 Fedora Update System 2017-03-13 15:19:32 UTC 
bind-dyndb-ldap-11.1-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f6f66523b8
Comment 16 Fedora Update System 2017-03-14 03:22:05 UTC 
bind-dyndb-ldap-11.1-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-f6f66523b8
Comment 17 Tomas Krizek 2017-03-14 11:03:20 UTC 
I've removed this bug from Fedora Update System, since it's filed for RHEL.
Comment 19 Scott Poore 2017-05-25 16:33:57 UTC 
This appears to be fixed.

Verified.

Version ::

Results ::
Comment 20 Scott Poore 2017-05-25 18:07:30 UTC 
Verified.

Version ::

ipa-server-4.5.0-13.el7.x86_64

Results ::


On rhel7.4 server, with fresh install, I tried ipa shutdown with dirsrv already down.

[root@rhel7-4 yum.repos.d]# systemctl stop dirsrv@EXAMPLE-COM

[root@rhel7-4 yum.repos.d]# ipactl stop
Stopping ipa-dnskeysyncd Service
Stopping ipa-otpd Service
Stopping pki-tomcatd Service
Stopping ntpd Service
Stopping ipa-custodia Service
Stopping httpd Service
Stopping named Service
Stopping kadmin Service
Stopping krb5kdc Service
Stopping Directory Service
ipa: INFO: The ipactl command was successful




From /var/log/messages:

May 25 11:30:54 rhel7-4 systemd: Stopping Berkeley Internet Name Domain (DNS) with native PKCS#11...
May 25 11:30:54 rhel7-4 named-pkcs11[11179]: received control channel command 'stop'
May 25 11:30:54 rhel7-4 named-pkcs11[11179]: shutting down: flushing changes
May 25 11:30:54 rhel7-4 named-pkcs11[11179]: stopping command channel on 127.0.0.1#953
May 25 11:30:54 rhel7-4 named-pkcs11[11179]: stopping command channel on ::1#953
May 25 11:30:54 rhel7-4 named-pkcs11[11179]: unloading DynDB instance 'ipa'
May 25 11:30:54 rhel7-4 named-pkcs11[11179]: zone example.com/IN: shutting down
May 25 11:30:54 rhel7-4 named-pkcs11[11179]: no longer listening on ::#53
May 25 11:30:54 rhel7-4 named-pkcs11[11179]: no longer listening on 127.0.0.1#53
May 25 11:30:54 rhel7-4 named-pkcs11[11179]: no longer listening on 192.168.122.74#53
May 25 11:30:54 rhel7-4 named-pkcs11[11179]: exiting




And I also ran an upgrade from 7.3 to 7.4 and did not see a named crash.  From the log:

May 25 12:11:54 master named-pkcs11[4161]: received control channel command 'stop'
May 25 12:11:54 master named-pkcs11[4161]: shutting down: flushing changes
May 25 12:11:54 master named-pkcs11[4161]: stopping command channel on 127.0.0.1#953
May 25 12:11:54 master named-pkcs11[4161]: stopping command channel on ::1#953
May 25 12:11:54 master named-pkcs11[4161]: unloading DynDB instance 'ipa'
May 25 12:11:54 master named-pkcs11[4161]: zone testrelm.test/IN: shutting down
May 25 12:11:54 master named-pkcs11[4161]: no longer listening on ::#53
May 25 12:11:54 master named-pkcs11[4161]: no longer listening on 127.0.0.1#53
May 25 12:11:54 master named-pkcs11[4161]: no longer listening on 192.168.122.71#53
May 25 12:11:54 master named-pkcs11[4161]: exiting
May 25 12:11:54 master systemd: Stopped Berkeley Internet Name Domain (DNS) with native PKCS#11.
May 25 12:11:54 master systemd: Stopped Berkeley Internet Name Domain (DNS) with native PKCS#11.
May 25 12:11:54 master systemd: Stopping Kerberos 5 Password-changing and Administration...
May 25 12:11:54 master systemd: kadmin.service: main process exited, code=exited, status=2/INVALIDARGUMENT
May 25 12:11:54 master systemd: Stopped Kerberos 5 Password-changing and Administration.
May 25 12:11:54 master systemd: Unit kadmin.service entered failed state.
May 25 12:11:54 master systemd: kadmin.service failed.
May 25 12:11:54 master systemd: Stopping Kerberos 5 KDC...
May 25 12:11:54 master systemd: Stopped Kerberos 5 KDC.
May 25 12:11:54 master systemd: Stopping 389 Directory Server TESTRELM-TEST....


It should be noted that it looked like DS stopped after named.  So, this may not even be a typical possible issue during upgrade anymore due to other changes.

Marking verified and as sanity only.
Comment 21 errata-xmlrpc 2017-08-01 19:27:49 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://access.redhat.com/errata/RHBA-2017:2120
Note You need to log in before you can comment on or make changes to this bug.