From owner-freebsd-apache@FreeBSD.ORG  Fri Jan 12 16:37:13 2007
Return-Path: <owner-freebsd-apache@FreeBSD.ORG>
X-Original-To: freebsd-apache@freebsd.org
Delivered-To: freebsd-apache@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 9071616A4AB
	for <freebsd-apache@freebsd.org>; Fri, 12 Jan 2007 16:37:13 +0000 (UTC)
	(envelope-from burnham@process.com)
Received: from beacon.PSC.process.com (beacon.psc.process.com [192.42.95.237])
	by mx1.freebsd.org (Postfix) with ESMTP id 5205A13C4A8
	for <freebsd-apache@freebsd.org>; Fri, 12 Jan 2007 16:37:13 +0000 (UTC)
	(envelope-from burnham@process.com)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Fri, 12 Jan 2007 11:28:32 -0500
Message-ID: <3EF96AF20489A34296050FBD5C36ECB984E50A@beacon.PSC.process.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: lockf status on Apache processes on 5.4-STABLE, apache 2.2.3
thread-index: Acc2Zjr6kIm9SR0vR9e/sd62BtZZzQ==
From: "Zach Burnham" <burnham@process.com>
To: <freebsd-apache@freebsd.org>
Subject: lockf status on Apache processes on 5.4-STABLE, apache 2.2.3
X-BeenThere: freebsd-apache@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Support of apache-related ports  <freebsd-apache.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-apache>, 
	<mailto:freebsd-apache-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-apache>
List-Post: <mailto:freebsd-apache@freebsd.org>
List-Help: <mailto:freebsd-apache-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-apache>,
	<mailto:freebsd-apache-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jan 2007 16:37:13 -0000

Hello everyone.

I've had an issue with an internal web server here.  Occasionally it'll
be unresponsive to http requests and will need to be restarted, or will
just be annoyingly slow.

In our investigations we've seen that there are a bunch of httpd
processes in "lockf" status.  The server load is near-zero, and none of
the lockf status processes appear to be consuming any resources past
their memory footprint.

The only information I've been able to find is regarding the Listen
directive; specifically, to set it to "Listen *:80".  We also handle
https traffic, so ours is set to "Listen *:80 *:443". =20

Do any of you have any suggestions as to what we can look at from here?
Or failing that, is there a way to see what files are open and which
process has opened them, or other status information that might point us
at the right thing?

TIA.

Zach