|Summary:||bind crash on 'reconfig' at resolver.c:7384|
|Product:||[Fedora] Fedora||Reporter:||Bill McGonigle <bill-bugzilla.redhat.com>|
|Component:||bind||Assignee:||Adam Tkac <atkac>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2008-11-27 10:32:54 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Bill McGonigle 2008-03-07 04:12:25 UTC
Comment 1 Adam Tkac 2008-03-10 11:18:42 UTC
b2 is in testing repository now (see https://bugzilla.redhat.com/show_bug.cgi?id=400461#c27). Would it be possible try it, please? From changelog it seems that some fix might be related to this issue.
Comment 2 Bill McGonigle 2008-03-12 02:29:39 UTC
Thanks. I've installed b2 and will report here (n theory, with a core) if I see another crash, though I don't know how to reproduce it.
Comment 3 Fedora Update System 2008-04-29 20:59:38 UTC
bind-9.5.0-26.b3.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update bind'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-3402
Comment 4 Bill McGonigle 2008-05-09 04:46:16 UTC
Another segfault today using the version from testing, but without the debugging info this time: May 5 14:45:01 borlaug kernel: named: segfault at dededede eip 00170c23 esp b7f26010 error 5 I also boned the aforementioned permissions, so didn't get a core (doh!). I think I've fixed them now: #ls -ld /var/named drwxrwxr-x 7 root named 4096 Mar 11 22:26 /var/named/ but would appreciate notice to the contrary. I do a reconfig every */15, so the timestamps line up to suggest this is the same problem.
Comment 5 Adam Tkac 2008-05-09 11:20:35 UTC
Yes, /var/named has to be writable by named user when you want core file. Segfault written above is different problem than original one. Attach core file when next segfault occurs, please. Thanks
Comment 6 Bug Zapper 2008-11-26 10:03:09 UTC
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. 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 '8'. 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 8'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 8 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 7 Bill McGonigle 2008-11-26 20:40:25 UTC
AFAICT, this update: Jul 10 05:34:43 Updated: bind-libs - 32:9.5.0-28.P1.fc8.i386 Jul 10 05:34:56 Updated: bind - 32:9.5.0-28.P1.fc8.i386 Jul 10 05:35:23 Updated: bind-utils - 32:9.5.0-28.P1.fc8.i386 Jul 10 05:35:29 Updated: bind-chroot - 32:9.5.0-28.P1.fc8.i386 solved the issue. At least it hasn't recurred since then. Note, I believe the updates are changing /var/named to 750,root:named which stops potentially useful cores from being written (needs to be 770). Not sure if that's another bug or design.
Comment 8 Adam Tkac 2008-11-27 10:32:54 UTC
(In reply to comment #7) > AFAICT, this update: > > Jul 10 05:34:43 Updated: bind-libs - 32:9.5.0-28.P1.fc8.i386 > Jul 10 05:34:56 Updated: bind - 32:9.5.0-28.P1.fc8.i386 > Jul 10 05:35:23 Updated: bind-utils - 32:9.5.0-28.P1.fc8.i386 > Jul 10 05:35:29 Updated: bind-chroot - 32:9.5.0-28.P1.fc8.i386 > > solved the issue. At least it hasn't recurred since then. Note, I believe the Thanks for feedback, closing this bug > updates are changing /var/named to 750,root:named which stops potentially > useful cores from being written (needs to be 770). Not sure if that's another > bug or design. It is intentional to have /var/named non-writable by named user.