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 2126912 - named-pkcs11 crashing into dns-pkcs11 library red-black tree [bind rhel-9.2.0]
Summary: named-pkcs11 crashing into dns-pkcs11 library red-black tree [bind rhel-9.2.0]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: bind
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Menšík
QA Contact: Petr Sklenar
URL:
Whiteboard:
Depends On: 2101712 2131784
Blocks: 2126877 2129844
TreeView+ depends on / blocked
 
Reported: 2022-09-14 18:20 UTC by Petr Menšík
Modified: 2023-05-09 08:47 UTC (History)
8 users (show)

Fixed In Version: bind-9.16.23-11.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2101712
Environment:
Last Closed: 2023-05-09 07:40:26 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
candidate patch for 9.16 (7.02 KB, patch)
2022-09-14 18:25 UTC, Petr Menšík
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/centos-stream/rpms bind merge_requests 12 0 None opened Have dns_zt_apply lock the zone table 2022-11-10 10:28:08 UTC
Gitlab redhat/centos-stream/rpms bind merge_requests 16 0 None opened fixup! Have dns_zt_apply lock the zone table 2023-02-27 14:08:39 UTC
Red Hat Issue Tracker RHELPLAN-133989 0 None None None 2022-09-14 18:23:09 UTC
Red Hat Product Errata RHSA-2023:2261 0 None None None 2023-05-09 07:40:54 UTC

Comment 1 Petr Menšík 2022-09-14 18:25:00 UTC
Created attachment 1911843 [details]
candidate patch for 9.16

Comment 3 Petr Menšík 2022-09-27 17:21:03 UTC
I would recommend workaround until this is fixed. Systemd is able to restart the service on ABRT termination, where it was not intended to stop. It will still make limited outage, but much less noticeable than if waiting for manual restart.

Run command:
systemctl edit named.service

Then inside editor, write line between comments:
[Service]
Restart=on-abnormal

Save and quit the editor

Double check the change is active:
systemctl show named.service -p Restart

Comment 14 Petr Menšík 2023-02-27 14:23:41 UTC
Fixes by additional commit

Comment 19 errata-xmlrpc 2023-05-09 07:40:26 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 (Moderate: bind security and bug fix update), 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/RHSA-2023:2261


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