From owner-freebsd-isp  Mon May  5 20:23:43 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id UAA10811
          for isp-outgoing; Mon, 5 May 1997 20:23:43 -0700 (PDT)
Received: from srv1.thuntek.net (root@srv1.thuntek.net [206.206.98.18])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA10806
          for <freebsd-isp@FreeBSD.ORG>; Mon, 5 May 1997 20:23:41 -0700 (PDT)
Received: from thor1.thuntek.net (abq1-18.thuntek.net [207.66.52.28]) by srv1.thuntek.net (8.8.4/8.6.12) with SMTP id VAA17405 for <freebsd-isp@FreeBSD.ORG>; Mon, 5 May 1997 21:23:33 -0600 (MDT)
Message-Id: <3.0.32.19970505212008.01103168@thuntek.net>
X-Sender: thor@thuntek.net
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Mon, 05 May 1997 21:23:53 -0600
To: freebsd-isp@FreeBSD.ORG
From: Scott Halbert <thor@thuntek.net>
Subject: Apache Socket Starvation Bug in 1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Is anyone familiar with the problems with Apache versions 1.2 with socket
starvation?  The problem manifests itself as the server locking itself up
and clients hanging with "waiting for reply".  For me a KILL -HUP will get
things going again.

To quote the apacheweek article, "This problem only affects systems which 
do not define USE_FLOCK_SERIALIZED_ACCEPT or USE_FCNTL_SERIALIZED_ACCEPT
in conf.h (this includes SunOS 4, FreeBSD, BSDI and some others)."

Here are some URLS documenting the bug:

	http://www.apache.org/bugdb.cgi/full/467
	http://www.apacheweek.com/issues/97-04-25

My problem is that the Apache workaround does not work for me.  Turning
on USE_FLOCK_SERIALIZED_ACCEPT does not help and USE_FCNTL_SERIALIZED_ACCEPT
hangs the server immediately.

It sure seems to me that I've got something unique in my configuration.
If this happened to all apache 1.2 servers under FreeBSD, I'd hear this
group freaking out.  I daresay that a very high majority of FreeBSD ISPs
use Apache. Maybe some of you have seen it and were in the same boat?

This problem is upsetting my customers and making me pull my hair out.

Maybe this is not exactly the bug I'm chasing, though it sure looks like
it.  Maybe I've got my timeouts and idles messed up in my configuration
file.

Thanks!

---Scott Halbert
Thunder Network Technologies, Inc.