Bug 1371891

Summary: [abrt] bind-pkcs11: assertion_failed(): named-pkcs11 killed by SIGABRT
Product: [Fedora] Fedora Reporter: Alvin <alvin>
Component: bindAssignee: Petr Menšík <pemensik>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: kim.eirik, mruprich, msehnout, thozza, vonsch, zdohnal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/afac5fe129f46f816ef6a642eb060d0380ab885a
Whiteboard: abrt_hash:b222c57b67cda3b2d7503761d8c0a23ee4b3710f;VARIANT_ID=server;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 16:57:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Alvin 2016-08-31 11:38:26 UTC
Description of problem:
This crash seems to be random.

Version-Release number of selected component:
bind-pkcs11-9.10.4-1.P2.fc24

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        /usr/sbin/named-pkcs11 -u named
crash_function: assertion_failed
executable:     /usr/sbin/named-pkcs11
global_pid:     3424
kernel:         4.6.6-300.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 3
type:           CCpp
uid:            25

Truncated backtrace:
Thread no. 1 (8 frames)
 #2 assertion_failed at ./main.c:232
 #3 isc_assertion_failed at assertions.c:58
 #4 dns_rdataset_first at rdataset.c:268
 #5 fctx_getaddresses at resolver.c:3277
 #6 fctx_try at resolver.c:3653
 #7 resquery_connected at resolver.c:2683
 #8 dispatch at task.c:1128
 #9 run at task.c:1300

Comment 1 Alvin 2016-08-31 11:38:34 UTC
Created attachment 1196311 [details]
File: backtrace

Comment 2 Alvin 2016-08-31 11:38:35 UTC
Created attachment 1196312 [details]
File: cgroup

Comment 3 Alvin 2016-08-31 11:38:37 UTC
Created attachment 1196313 [details]
File: core_backtrace

Comment 4 Alvin 2016-08-31 11:38:39 UTC
Created attachment 1196314 [details]
File: dso_list

Comment 5 Alvin 2016-08-31 11:38:40 UTC
Created attachment 1196315 [details]
File: environ

Comment 6 Alvin 2016-08-31 11:38:42 UTC
Created attachment 1196316 [details]
File: limits

Comment 7 Alvin 2016-08-31 11:38:44 UTC
Created attachment 1196317 [details]
File: maps

Comment 8 Alvin 2016-08-31 11:38:45 UTC
Created attachment 1196318 [details]
File: mountinfo

Comment 9 Alvin 2016-08-31 11:38:47 UTC
Created attachment 1196319 [details]
File: namespaces

Comment 10 Alvin 2016-08-31 11:38:49 UTC
Created attachment 1196320 [details]
File: open_fds

Comment 11 Alvin 2016-08-31 11:38:50 UTC
Created attachment 1196321 [details]
File: proc_pid_status

Comment 12 Alvin 2016-08-31 11:38:52 UTC
Created attachment 1196322 [details]
File: var_log_messages

Comment 13 Alvin 2016-08-31 11:40:16 UTC
Restarting the named-pkcs11.service is possible after the crash.

Comment 14 kim.eirik@gmail.com 2016-11-04 15:43:20 UTC
Similar problem has been detected:

Regular restart of IPA Server (ipactl restart).
Same issue occurs when rebooting the server.
"ipactl start" can be run about 3-4 times, and named will actually start successfully in the end.
Suspecting the errors is due to transfer of zones on startup.

reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        /usr/sbin/named-pkcs11 -u named
crash_function: assertion_failed
executable:     /usr/sbin/named-pkcs11
global_pid:     2291
kernel:         4.8.4-200.fc24.x86_64
package:        bind-pkcs11-9.10.4-2.P3.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         named-pkcs11 killed by SIGABRT
runlevel:       N 3
type:           CCpp
uid:            25

Comment 15 Fedora Admin XMLRPC Client 2016-12-01 14:20:58 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 16 Fedora End Of Life 2017-07-25 22:46:09 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 17 Fedora End Of Life 2017-08-08 16:57:04 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.