From owner-freebsd-current@FreeBSD.ORG Fri Mar 5 06:47:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A61816A4FD for ; Fri, 5 Mar 2004 06:47:36 -0800 (PST) Received: from bas.flux.utah.edu (bas.flux.utah.edu [155.98.60.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B243743D46 for ; Fri, 5 Mar 2004 06:47:35 -0800 (PST) (envelope-from mac@macnewbold.com) Received: from localhost (localhost [127.0.0.1]) by bas.flux.utah.edu (8.12.9/8.12.5) with ESMTP id i25ElYdU017197; Fri, 5 Mar 2004 07:47:34 -0700 (MST) (envelope-from mac@macnewbold.com) Date: Fri, 5 Mar 2004 07:47:34 -0700 (MST) From: Mac Newbold X-X-Sender: newbold@bas.flux.utah.edu To: freebsd-current@freebsd.org Message-ID: <20040305074521.V91802@bas.flux.utah.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: uthread_kern.c problems (still) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Mar 2004 14:47:36 -0000 I've been getting bitten a lot lately by a bug in uthread_kern.c that keeps causing my apache processes to run away, until I kill them. (dmesg indicates it has also been happening to fstat processes too, but they die instead of running away.) The apache error log indicates this: [Tue Mar 02 09:54:35 2004] [notice] child pid 52132 exit signal Abort trap (6) 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) dmesg gets stuff like this: pid 40525 (fstat), uid 0: exited on signal 11 pid 40377 (httpd), uid 80: exited on signal 6 pid 39306 (httpd), uid 80: exited on signal 6 pid 40770 (httpd), uid 80: exited on signal 6 pid 41064 (fstat), uid 0: exited on signal 11 I'm running apache2, mysql, php, and openssl: Apache/2.0.48 (Unix) mod_perl/1.99_12 Perl/v5.6.1 PHP/4.3.4 mod_ssl/2.0.48 OpenSSL/0.9.7a Server The crashes come most often running php scripts, and certain scripts can be very reliable in causing the problem. > uname -a FreeBSD 5.2-CURRENT FreeBSD 5.2-CURRENT #3: Thu Feb 26 17:50:22 MST 2004 root@tahiti.dmedia.ws:/usr/obj/usr/src/sys/GENERIC i386 It started after I had been using 5.1-p10 for several months, so I upgraded to the lastest current (post 5.2-RELEASE) a few days ago, and the problem was still there. Google reveals that people have been seeing crashes from it for at least 8 months now, going back to June 2003, most often with gnucash for some reason, but with apache as well. Related messages: http://lists.freebsd.org/pipermail/freebsd-hackers/2003-November/004121.html http://lists.freebsd.org/pipermail/freebsd-current/2004-January/017764.html http://lists.freebsd.org/pipermail/freebsd-gnome/2004-January/004505.html http://lists.freebsd.org/pipermail/freebsd-ports/2003-June/002248.html http://lists.freebsd.org/pipermail/freebsd-ports/2003-July/002839.html Any ideas for solutions or workarounds would be greatly appreciated. If others are having this problem, and you'd like something to keep your runaway processes under control, I've got a script for it now. Thanks, Mac -- Mac Newbold mac@macnewbold.com MNE - Mac Newbold Enterprises, LLC MNE Dmedia Bluelune Web Guide