Bug 1666178

Summary: [abrt] bind: library_fatal_error(): named killed by SIGABRT
Product: [Fedora] Fedora Reporter: JDP803
Component: bindAssignee: Petr Menšík <pemensik>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: anon.amish, JDP803, mruprich, msehnout, pemensik, pzhukov, thozza, vonsch, zdohnal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/67b68b8c224e059d90a984f80e8e8edb8a49318f
Whiteboard: abrt_hash:d4e4344ff5517473dd84cf6adc9f032e53542c54;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-27 23:34:23 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:
Bug Depends On:    
Bug Blocks: 1736762, 1779589    
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description JDP803 2019-01-15 06:58:56 UTC 
Description of problem:


Version-Release number of selected component:
32:bind-9.11.4-10.P2.fc29

Additional info:
reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        /usr/sbin/named -u named -c /etc/named.conf
crash_function: library_fatal_error
executable:     /usr/sbin/named
journald_cursor: s=fc8a645917e441d48e9f70c91780c572;i=1b61e;b=6ad28c9ea57b40008c35c23fcd14fda5;m=c45c988d91;t=57f76005e6a14;x=4dfe2d8890b2f553
kernel:         4.19.13-300.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            25

Potential duplicate: bug 855938
Comment 1 JDP803 2019-01-15 06:58:58 UTC 
Created attachment 1520652 [details]
File: backtrace
Comment 2 JDP803 2019-01-15 06:58:59 UTC 
Created attachment 1520653 [details]
File: cgroup
Comment 3 JDP803 2019-01-15 06:59:00 UTC 
Created attachment 1520654 [details]
File: core_backtrace
Comment 4 JDP803 2019-01-15 06:59:01 UTC 
Created attachment 1520655 [details]
File: cpuinfo
Comment 5 JDP803 2019-01-15 06:59:02 UTC 
Created attachment 1520656 [details]
File: dso_list
Comment 6 JDP803 2019-01-15 06:59:03 UTC 
Created attachment 1520657 [details]
File: environ
Comment 7 JDP803 2019-01-15 06:59:05 UTC 
Created attachment 1520658 [details]
File: limits
Comment 8 JDP803 2019-01-15 06:59:06 UTC 
Created attachment 1520659 [details]
File: maps
Comment 9 JDP803 2019-01-15 06:59:07 UTC 
Created attachment 1520660 [details]
File: mountinfo
Comment 10 JDP803 2019-01-15 06:59:08 UTC 
Created attachment 1520661 [details]
File: open_fds
Comment 11 JDP803 2019-01-15 06:59:09 UTC 
Created attachment 1520662 [details]
File: proc_pid_status
Comment 12 Petr Menšík 2019-10-21 11:49:14 UTC 
Probably related to bug #1736762. Do we know how to trigger this problem?
Comment 13 Ben Cotton 2019-10-31 18:45:14 UTC 
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 14 Ben Cotton 2019-11-27 23:34:23 UTC 
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.