From owner-freebsd-ports@FreeBSD.ORG Thu Jul 15 05:41:33 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 E4AAC16A4CE for ; Thu, 15 Jul 2004 05:41:33 +0000 (GMT) Received: from ms-smtp-03.rdc-nyc.rr.com (ms-smtp-03-smtplb.rdc-nyc.rr.com [24.29.109.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67B5D43D49 for ; Thu, 15 Jul 2004 05:41:33 +0000 (GMT) (envelope-from freebsd@toyingwithfate.com) Received: from toyingwithfate.com (66-108-61-89.nyc.rr.com [66.108.61.89]) i6F5fV20016640 for ; Thu, 15 Jul 2004 01:41:31 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by toyingwithfate.com (8.12.10/8.12.10) with ESMTP id i6F5dCZY004459 for freebsd-ports@freebsd.org; Thu, 15 Jul 2004 00:39:36 -0500 (EST) (envelope-from freebsd@toyingwithfate.com) Date: Thu, 15 Jul 2004 00:39:12 -0500 (EST) Message-Id: <200407150539.i6F5dCZY004459@toyingwithfate.com> From: Will McCutcheon To: freebsd-ports@freebsd.org X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: '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: Thu, 15 Jul 2004 05:41:34 -0000 I have a server running 5.2.1-RELEASE-p8 and just started using Apache 2.0.50 with PHP 4.3.7-3. I immediately ran into a strange problem I've never seen before, where when I send mail in IMP (a webmail system I run on this server) the child Apache process crashes with the following error: Fatal error 'Unable to read from thread kernel pipe' at line 1100 in file /usr/src/lib/libc_r/uthread/uthread_kern.c (errno = 0) [Wed Jul 14 22:29:41 2004] [notice] child pid 3686 exit signal Abort trap (6) Anyone have any ideas as to what's causing this? I found that error message in discussions about gnucash and xscreensaver-demo, but with no answers. I'm not sure whether the problem lies in Apache or somewhere else, but because I'm experiencing it in Apache I'm reporting it here on the ports list. Thanks! W