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.

Description of problem:
abrt-hook-ccpp[24936]: Process 7710 (named-pkcs11) of user 25 killed by SIGABRT - dumping core
Mar  4 08:23:51 ipa-2 systemd[1]: named-pkcs11.service: main process exited, code=killed, status=6/ABRT
Mar  4 08:23:51 ipa-2 systemd[1]: Unit named-pkcs11.service entered failed state.
Mar  4 08:23:51 ipa-2 systemd[1]: named-pkcs11.service failed.


Version-Release number of selected component (if applicable):
bind-pkcs11-9.11.4-26.P2.el7

How reproducible:
On the client's side, crashes once a week or two.

Expected results:
No crash

Additional info:
Sosreport and coredump with backtrace in the attached case

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 (bind bug fix and enhancement 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/RHBA-2022:0624

If there are any remaining crashes, I would recommend automatic named-pkcs11 restarting on crash. It would not correct the issue completely, but should minimize impact an occasional crash might have.

As root edit named-pkcs11.service:

systemctl edit named-pkcs11.service

# this will open an editor, save following two line in it
[Service]
Restart=on-abnormal

# save and exit the editor

Now named-pkcs11.service would get automatically restarted by the systemd if it terminates with SIGABRT (core dumped). That is common in named terminating with any assertion failure.
It is still worth reporting those crashes, but they are hard to find correctly. This workaround should keep your service available if crashes are only occasional.