Hide Forgot
Description of problem: To reproduce: Boot server wait a few minutes 2 services fail at boot: - ipa-otpd Service - ipa-dnskeysyncd Service After manually starting those 2, everything works, but suddenly ipactl will fail to start the pki-tomcatd service (which was running). After that, other IPA related services go down. 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: 879 kernel: 4.6.7-300.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: unknown type: CCpp uid: 25 Truncated backtrace: Thread no. 1 (6 frames) #2 assertion_failed at ./main.c:232 #3 isc_assertion_failed at assertions.c:58 #4 dispatch_recv at socket.c:3298 #5 process_fd at socket.c:3968 #6 process_fds at socket.c:4080 #7 watcher at socket.c:4326
Created attachment 1195940 [details] File: backtrace
Created attachment 1195941 [details] File: cgroup
Created attachment 1195942 [details] File: core_backtrace
Created attachment 1195943 [details] File: dso_list
Created attachment 1195944 [details] File: environ
Created attachment 1195945 [details] File: limits
Created attachment 1195946 [details] File: maps
Created attachment 1195947 [details] File: mountinfo
Created attachment 1195948 [details] File: namespaces
Created attachment 1195949 [details] File: open_fds
Created attachment 1195950 [details] File: proc_pid_status
Created attachment 1195951 [details] File: var_log_messages
I don't have any problem at boot, but occasionally, the named-pkcs11 process will die with SIGABRT.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.
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.