From owner-freebsd-ports@FreeBSD.ORG Fri Jul 16 05:32:57 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3FD916A4CE for ; Fri, 16 Jul 2004 05:32:57 +0000 (GMT) Received: from ms-smtp-02.rdc-nyc.rr.com (ms-smtp-02-smtplb.rdc-nyc.rr.com [24.29.109.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49AF943D2F for ; Fri, 16 Jul 2004 05:32:57 +0000 (GMT) (envelope-from freebsd@toyingwithfate.com) Received: from toyingwithfate.com (66-108-61-89.nyc.rr.com [66.108.61.89]) i6G5WsBM015133 for ; Fri, 16 Jul 2004 01:32:55 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by toyingwithfate.com (8.12.9p1/8.12.9) with ESMTP id i6G5MPKC052059 for freebsd-ports@freebsd.org; Fri, 16 Jul 2004 01:29:26 -0400 (EDT) (envelope-from freebsd@toyingwithfate.com) Date: Fri, 16 Jul 2004 01:22:25 -0400 (EDT) Message-Id: <200407160529.i6G5MPKC052059@toyingwithfate.com> To: freebsd-ports@freebsd.org From: Will McCutcheon In-Reply-To: <20040715225910.6f14220f.sheepkiller@cultdeadsheep.org> References: <20040715225910.6f14220f.sheepkiller@cultdeadsheep.org> <20040715214806.4bc8a4ee.sheepkiller@cultdeadsheep.org> <200407150539.i6F5dCZY004459@toyingwithfate.com> <200407152004.i6FK3eKC049113@toyingwithfate.com> X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Scanned: clamd / ClamAV version 0.72, clamav-milter version 0.72 on toyingwithfate.com X-Virus-Status: Clean Subject: Re: 'Unable to read from thread kernel pipe' error in Apache X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jul 2004 05:32:57 -0000 Clement Laforet wrote: > Can you do a "ldd /usr/local/sbin/httpd" ? $ ldd /usr/local/sbin/httpd /usr/local/sbin/httpd: libz.so.2 => /lib/libz.so.2 (0x280bd000) libssl.so.3 => /usr/lib/libssl.so.3 (0x280cb000) libcrypto.so.3 => /lib/libcrypto.so.3 (0x280fd000) libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9 (0x2820b000) libexpat.so.5 => /usr/local/lib/libexpat.so.5 (0x2821e000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x2823e000) libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x2832d000) libm.so.2 => /lib/libm.so.2 (0x2834a000) libcrypt.so.2 => /lib/libcrypt.so.2 (0x28363000) libc.so.5 => /lib/libc.so.5 (0x2837c000) > Futhermore, it will be great if you can provide me a backtrace. It took me some research to figure out how to properly debug a crashing Apache child, but I ultimately figured it out by combining your instructions with the ones found here: http://httpd.apache.org/dev/debugging.html Here's what I got: (gdb) bt #0 0x283d1dcf in kill () from /lib/libc.so.5 #1 0x283c6878 in raise () from /lib/libc.so.5 #2 0x2843ef82 in abort () from /lib/libc.so.5 #3 0x2907f565 in _thread_exit () from /usr/lib/libc_r.so.5 #4 0x2907d345 in _thread_kern_sig_undefer () from /usr/lib/libc_r.so.5 #5 0x2907ca94 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #6 0x2907c445 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 Anything especially revealing? Thanks for helping me out! W