Bug 808269 - [abrt] bind-9.8.2-0.2.rc1.fc16: __GI_raise: Process /usr/sbin/named was killed by signal 6 (SIGABRT)
[abrt] bind-9.8.2-0.2.rc1.fc16: __GI_raise: Process /usr/sbin/named was kille...
Product: Fedora
Classification: Fedora
Component: bind-dyndb-ldap (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Adam Tkac
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-03-29 21:49 EDT by James Cape
Modified: 2013-04-30 19:51 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-01-16 05:44:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: var_log_messages (7.61 KB, text/plain)
2012-03-29 21:49 EDT, James Cape
no flags Details
File: maps (21.43 KB, text/plain)
2012-03-29 21:49 EDT, James Cape
no flags Details
File: backtrace (9.60 KB, text/plain)
2012-03-29 21:49 EDT, James Cape
no flags Details

  None (edit)
Description James Cape 2012-03-29 21:49:45 EDT
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        /usr/sbin/named -u named
crash_function: __GI_raise
executable:     /usr/sbin/named
kernel:         3.1.6-1.fc16.x86_64
pid:            20341
pwd:            /var/named
reason:         Process /usr/sbin/named was killed by signal 6 (SIGABRT)
time:           Thu 29 Mar 2012 09:41:28 PM EDT
uid:            25
username:       named

backtrace:      Text file, 9832 bytes
maps:           Text file, 21947 bytes
var_log_messages: Text file, 7794 bytes


:/usr/lib64/sasl2/libdigestmd5.so.2.0.23 cyrus-sasl-md5-2.1.23-27.fc16.x86_64 (Fedora Project) 1332970768
:/usr/lib64/sasl2/libanonymous.so.2.0.23 cyrus-sasl-lib-2.1.23-27.fc16.x86_64 (Fedora Project) 1332970518
:/usr/lib64/sasl2/libcrammd5.so.2.0.23 cyrus-sasl-md5-2.1.23-27.fc16.x86_64 (Fedora Project) 1332970768
:/usr/lib64/sasl2/libgssapiv2.so.2.0.23 cyrus-sasl-gssapi-2.1.23-27.fc16.x86_64 (Fedora Project) 1332970535
:/usr/sbin/named bind-32:9.8.2-0.2.rc1.fc16.x86_64 (Fedora Project) 1328909816
:/lib64/libnss_files-2.14.90.so glibc-2.14.90-24.fc16.6.x86_64 (Fedora Project) 1332970416
:/usr/lib64/sasl2/libsasldb.so.2.0.23 cyrus-sasl-lib-2.1.23-27.fc16.x86_64 (Fedora Project) 1332970518
:/usr/lib64/bind/ldap.so bind-dyndb-ldap-1.1.0-0.8.a2.fc16.x86_64 (Fedora Project) 1332289352

Comment 1 James Cape 2012-03-29 21:49:48 EDT
Created attachment 573851 [details]
File: var_log_messages
Comment 2 James Cape 2012-03-29 21:49:50 EDT
Created attachment 573852 [details]
File: maps
Comment 3 James Cape 2012-03-29 21:49:51 EDT
Created attachment 573853 [details]
File: backtrace
Comment 4 Adam Tkac 2012-03-30 04:09:40 EDT
This seems like a memory leak in bind-dyndb-ldap plugin for me (or in BIND itself).

Can you please update the bind-dyndb-ldap package to the latest version and check if it's OK (via `yum update --enablerepo updates-testing bind-dyndb-ldap`)? It contains some memory leak fixes.

Additionally, please add the "OPTIONS='-m record'" option to the /etc/sysconfig/named. With this flag, named will write which memory is not free()-ed on exit in case this bug is still unfixed. If this don't happen again, you can remove the flag and we can close this bug as already fixed. Thank you in advance.
Comment 5 Fedora End Of Life 2013-01-16 05:20:35 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 

Note You need to log in before you can comment on or make changes to this bug.