This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.3.16-1: Apache 1.3.24 not rotating/lockup problem
- From: "Dylan Cuthbert" <dylan at q-games dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 20 Feb 2003 15:51:20 +0900
- Subject: Re: 1.3.16-1: Apache 1.3.24 not rotating/lockup problem
- References: <3DE48797.firstname.lastname@example.org> <3DE4F8EE.8E7CAE83@wapme-systems.de> <20021127185855.O1398@cygbert.vinschen.de> <3DE59878.A9D64756@wapme-systems.de> <20021128101359.A23323@cygbert.vinschen.de>
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
Q-Games, Dylan Cuthbert.
"Corinna Vinschen" <corinna-cygwin at cygwin dot com> wrote in message
news:20021128101359 dot A23323 at cygbert dot vinschen dot de dot dot dot
> 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
> > > 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 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