Description of problem: named was started on new hardware with system clock set to 2009-01-01. The daemon couldn't resolve anything (I guess because of some kind of certificate problems due to wrong system time). I've tried "service named restart" and this crash was reported. Version-Release number of selected component: bind-9.9.4-12.P2.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/sbin/named -u named -4 crash_function: assertion_failed executable: /usr/sbin/named kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 25 Truncated backtrace: Thread no. 1 (3 frames) #2 assertion_failed at ./main.c:219 #3 isc_assertion_failed at assertions.c:57 #4 isc__mem_destroy at mem.c:1249
Created attachment 883074 [details] File: backtrace
Created attachment 883075 [details] File: cgroup
Created attachment 883076 [details] File: core_backtrace
Created attachment 883077 [details] File: dso_list
Created attachment 883078 [details] File: environ
Created attachment 883079 [details] File: limits
Created attachment 883080 [details] File: maps
Created attachment 883081 [details] File: open_fds
Created attachment 883082 [details] File: proc_pid_status
Created attachment 883083 [details] File: var_log_messages
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.