Bug 1084719

Summary: [abrt] bind: assertion_failed(): named killed by SIGABRT
Product: [Fedora] Fedora Reporter: Leszek Matok <lam>
Component: bindAssignee: Tomáš Hozza <thozza>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: psimerda, thozza, vonsch
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3f567655a7e8ace28d11fbb113f9cc062118ddbc
Whiteboard: abrt_hash:3446c89773e21d548d48d1a7ccca05fa36c44951
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 19:54:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
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: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Leszek Matok 2014-04-05 22:24:02 UTC
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

Comment 1 Leszek Matok 2014-04-05 22:24:07 UTC
Created attachment 883074 [details]
File: backtrace

Comment 2 Leszek Matok 2014-04-05 22:24:09 UTC
Created attachment 883075 [details]
File: cgroup

Comment 3 Leszek Matok 2014-04-05 22:24:10 UTC
Created attachment 883076 [details]
File: core_backtrace

Comment 4 Leszek Matok 2014-04-05 22:24:12 UTC
Created attachment 883077 [details]
File: dso_list

Comment 5 Leszek Matok 2014-04-05 22:24:14 UTC
Created attachment 883078 [details]
File: environ

Comment 6 Leszek Matok 2014-04-05 22:24:16 UTC
Created attachment 883079 [details]
File: limits

Comment 7 Leszek Matok 2014-04-05 22:24:18 UTC
Created attachment 883080 [details]
File: maps

Comment 8 Leszek Matok 2014-04-05 22:24:21 UTC
Created attachment 883081 [details]
File: open_fds

Comment 9 Leszek Matok 2014-04-05 22:24:23 UTC
Created attachment 883082 [details]
File: proc_pid_status

Comment 10 Leszek Matok 2014-04-05 22:24:25 UTC
Created attachment 883083 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2015-05-29 11:28:34 UTC
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.

Comment 12 Fedora End Of Life 2015-06-29 19:54:36 UTC
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.