Red Hat Bugzilla – Bug 988108
[abrt] bind-9.9.3-3.P1.fc19: assertion_failed: Process /usr/sbin/named was killed by signal 6 (SIGABRT)
Last modified: 2016-06-21 15:10:49 EDT
Description of problem:
Not sure what happened.
But I had just restarted and ethernet port, and shortly there after,
I couldn't lookup host names any more.
Version-Release number of selected component:
cmdline: /usr/sbin/named -u named
runlevel: N 3
Thread no. 1 (9 frames)
#3 assertion_failed at ./main.c:219
#4 isc_assertion_failed at assertions.c:57
#5 dns_resolver_createfetch2 at resolver.c:8193
#6 dns_resolver_createfetch at resolver.c:8161
#7 zone_refreshkeys at zone.c:8590
#8 zone_maintenance at zone.c:8779
#9 zone_timer at zone.c:11362
#10 dispatch at task.c:1116
#11 run at task.c:1286
Created attachment 777898 [details]
Created attachment 777899 [details]
Created attachment 777900 [details]
Created attachment 777901 [details]
Created attachment 777902 [details]
Created attachment 777903 [details]
Created attachment 777904 [details]
Created attachment 777905 [details]
Created attachment 777906 [details]
Created attachment 777907 [details]
The logs are from the first time it happened, and it too has a network interface changing, and after that an automatic reload:
Jul 13 15:03:34 ipa named: listening on IPv4 interface ppp0, 10.235.176.232#53
Might be the reloads that is causing this, and they are issued by NetworkManager-dispatcher.
Named is running in an freeipa setup.
Niki, can you please set the debug level to higher (calling #rndc trace 5) and
attach the named log after crash?
Peter, it looks as some LDAP related issue, do you think it might be caused
by the bind-dyndb-ldap plugin?
(In reply to Tomas Hozza from comment #12)
> Peter, it looks as some LDAP related issue, do you think it might be caused
> by the bind-dyndb-ldap plugin?
I don't think that this is related to bind-dyndb-ldap. IMHO bind-dyndb-ldap can't load any zones because it is unable to establish connection to LDAP server.
My guess is that it crashed somewhere in BIND resolver without any relation to bind-dyndb-ldap.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.