From owner-freebsd-bugs Wed May 12 21: 0: 5 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 99535152B2 for ; Wed, 12 May 1999 21:00:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id VAA23287; Wed, 12 May 1999 21:00:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from cartserver.com (www2.cartserver.com [209.68.60.164]) by hub.freebsd.org (Postfix) with ESMTP id 63D5514D91 for ; Wed, 12 May 1999 20:59:20 -0700 (PDT) (envelope-from sigma@cartserver.com) Received: (from root@localhost) by cartserver.com (8.9.2/8.6.12) id AAA13748; Thu, 13 May 1999 00:03:47 -0400 (EDT) Message-Id: <199905130403.AAA13748@cartserver.com> Date: Thu, 13 May 1999 00:03:47 -0400 (EDT) From: Kevin Martin Reply-To: sigma@cartserver.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/11679: httpd and perl5 processes stuck in "nochan" eating CPU Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 11679 >Category: kern >Synopsis: httpd and perl5 processes stuck in "nochan" eating CPU >Confidential: yes >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed May 12 21:00:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Kevin Martin >Release: FreeBSD 3.1-STABLE i386 >Organization: pair Networks, Inc >Environment: Xeon 500 Mhz, 512Mb RAM, SCSI and IDE drives, running typical mod_ssl installation. >Description: httpd and perl5 processes enter "nochan" status and eat unlimited CPU capacity, while doing no useful work. Can only be cleaned up by "kill -9". We have developed a script to monitor for this and perform the kills. However, it is affecting performance and causing blank pages to be returned from runaway httpd processes. We have also seen this under FreeBSD 2.2.7-STABLE for extremely busy servers with lots of CGI activity. >How-To-Repeat: Just let the server run, even with only 2 hits/second. >Fix: Unknown; these processes are becoming stranded somehow by the kernel. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message