Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
From: "Dylan Cuthbert" <dylan AT q-games DOT com>
Subject: Re: 1.3.16-1: Apache 1.3.24 not rotating/lockup problem
Date: Thu, 20 Feb 2003 15:51:20 +0900
Lines: 65
Message-ID: <b31tt5$cn9$1@main.gmane.org>
References: <3DE48797 DOT 5030004 AT atrove DOT com> <3DE4F8EE DOT 8E7CAE83 AT wapme-systems DOT de> <20021127185855 DOT O1398 AT cygbert DOT vinschen DOT de> <3DE59878 DOT A9D64756 AT wapme-systems DOT de> <20021128101359 DOT A23323 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT main DOT gmane DOT org
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Any more information on this problem?  Anyone solved it?

server-status makes it obvious what's being said in this thread - ie. the
children forked by apache aren't allowing themselves to be re-used on a
different connection properly, hence they all eventually lock up (once
KeepAlive times out) and your web site goes down.

Corinna - simply set KeepAlive on, and the time out value to 10.  Then
access your index page, wait 10 seconds and then access it again... continue
this a few times and you will end up locking all the children up.  (they
work fine until the keepalive system tries to reset them to another
connection)

Regards

--
---------------------------------
Q-Games, Dylan Cuthbert.
http://www.q-games.com


"Corinna Vinschen" <corinna-cygwin AT cygwin DOT com> wrote in message
news:20021128101359 DOT A23323 AT cygbert DOT vinschen DOT de...
> On Thu, Nov 28, 2002 at 05:15:52AM +0100, Stipe Tolj wrote:
> > Corinna Vinschen schrieb:
> > >
> > > On Wed, Nov 27, 2002 at 05:55:10PM +0100, Stipe Tolj wrote:
> > > > > I guess the main apache process that is suppose to arbitrate the
> > > > > requests is not working properly with cygwin 1.3.16-1
> > > > >
> > > > > Has anyone else seen similar problems with apache?
> > > > > Has anything changed in cygwin that would cause such behavior?
> > > >
> > > > That exactly the question I'd like to hear from the core Cygwin
> > > > people. Corinna, may you pick this issue up?!
> > >
> > > Sure, if you post a *small* testcase to the ML which points to a
problem
> > > in Cygwin.  Other than that you should probably debug apache first.
> >
> > it seems *very* obious that it's a cygwin internal problem, since
> > *all* apache versions worked correctly up to cygwin 1.3.10-2 and then
> > the same behaviour, locking of httpd processes began.
>
> Cool.  I guess apache rans fine with b20.
>
> Guesswork isn't really helpful.  Sure there are errors in Cygwin as they
> are in apache as in any other big software project.  Coincidentally other
> applications might run better since 1.3.10.
>
> You know how that works, don't you?  You'll debug apache.  You'll find a
> problem.  You could find a workaround in apache by creating a Cygwin
> specific patch which also helps people running older versions of Cygwin.
> And/or you could create a small testcase which demonstrates the problem
> in Cygwin so that we have a chance to either fix it or demonstrate that
> it's correct behaviour.
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Developer                                mailto:cygwin AT cygwin DOT com
> Red Hat, Inc.
>



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/