[Bug 578934] New: named crashes on startup with segmentation fault in isc_file_isabsolute
http://bugzilla.novell.com/show_bug.cgi?id=578934 http://bugzilla.novell.com/show_bug.cgi?id=578934#c0 Summary: named crashes on startup with segmentation fault in isc_file_isabsolute Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: steve@srevilak.net QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=341884) --> (http://bugzilla.novell.com/attachment.cgi?id=341884) Transcript of GDB session showing named segmentation fault User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 I would like to report a named crash in OpenSUSE 11.2, aka $ uname -a Linux spud2 2.6.31.5-0.1-desktop #1 SMP PREEMPT 2009-10-26 15:49:03 +0100 x86_64 x86_64 x86_64 GNU/Linux This is a fresh installation on a Dell Z400 workstation. named crashes consistently on startup, segfaulting in isc_file_isabsolute(). I first noticed this when trying to start named via /etc/init.d/named, but I can reproduce the same behavior by running named directly from a command line: --------------------------------- $ touch /tmp/empty.conf $ sudo /usr/sbin/named -u named -g -c /tmp/empty.conf 10-Feb-2010 18:21:56.038 starting BIND 9.6.1-P3 -u named -g -c /tmp/empty.conf 10-Feb-2010 18:21:56.038 built with '--prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--localstatedir=/var' '--libdir=/usr/lib64' '--includedir=/usr/include/bind' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--with-openssl' '--enable-threads' '--with-libtool' '--enable-runidn' '--with-libxml2' '--with-dlz-mysql' 'CFLAGS=-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fno-strict-aliasing' 'LDFLAGS=-L/usr/lib64' Segmentation fault --------------------------------- Reproducible: Always Steps to Reproduce: 1. touch /tmp/empty.conf 2a. sudo /usr/sbin/named -u named -g -c /tmp/empty.conf - OR - 2b. sudo /usr/sbin/named -u named -g -c /etc/named.conf Actual Results: Program received signal SIGSEGV, Segmentation fault. 0x00007f5b2845bde0 in isc_file_isabsolute () from /usr/lib64/libisc.so.50 Expected Results: I expected named to start, read its configuration files, bind to port 53, and begin servicing DNS requests. I'm attaching a file called named-diagnostics.txt. This file contains - output of a gdb session where I reproduce the crash and give a stack trace - packaging information for named and libisc.so.50 (to show exactly which versions I'm using) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=578934 http://bugzilla.novell.com/show_bug.cgi?id=578934#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |ug@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=578934 http://bugzilla.novell.com/show_bug.cgi?id=578934#c1 Uwe Gansert <ug@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |steve@srevilak.net --- Comment #1 from Uwe Gansert <ug@novell.com> 2010-02-16 09:55:05 UTC --- do you have all updates installed? If not, please do so. It looks like a bug in apparmor that has been fixed. You can stop apparmor to test that. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=578934 http://bugzilla.novell.com/show_bug.cgi?id=578934#c2 Steve Revilak <steve@srevilak.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|steve@srevilak.net | --- Comment #2 from Steve Revilak <steve@srevilak.net> 2010-02-17 02:05:04 UTC --- Uwe, Thanks for looking at this. After seeing the segfault, my first instinct was to check for upgraded packages (i.e. "zypper update"). I allowed zypper to upgrade all of the packages it identified, then rebooted the machine. After reboot, the segmentation fault in isc_file_isabsolute was still consistently reproducible. I reinstalled OpenSUSE over the weekend. (I decided that I wanted to partition the disks differently. Since my initial installation was only a few days prior, a clean install seemed easiest.) After re-installing, named no longer segfaults on startup; named works perfectly well now. I had made notes during my first installation. With the exception of disk partitioning, I tried to follow the same procedure during my second installation. (In both cases, / was RAID 1, using mdadm.) Unfortunately, I don't know why the segfaults occurred in my first installation, but not the second. If the segmentation faults occur again, I will try disabling AppArmor as you suggested. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=578934 http://bugzilla.novell.com/show_bug.cgi?id=578934#c3 Uwe Gansert <ug@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #3 from Uwe Gansert <ug@novell.com> 2010-02-17 08:07:34 UTC --- Hm. Strange. I was not able to reproduce that either. So I close this now. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com