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
Message-ID:	<3DC26111.314D8CB0@wapme-systems.de>
Date:	Fri, 01 Nov 2002 12:10:09 +0100
From:	Stipe Tolj <tolj AT wapme-systems DOT de>
Organization:	Wapme Systems AG
X-Accept-Language:	de
MIME-Version:	1.0
To:	Uwe Mayer <merkosh AT hadiko DOT de>
CC:	cygwin AT cygwin DOT com
Subject:	Re: upgrading - apache fails
References:	<31992737 DOT 20021031222830 AT hadiko DOT de>

> I've been upgrading to cygwin 1.3.14-1. After the update the apache
> web server won't start up again. The /var/log/apache/error_log
> contains:
> 
> [Thu Oct 31 22:24:51 2002] [notice] Apache/1.3.24 (Cygwin) configured -- resuming normal operations
> [Thu Oct 31 22:24:51 2002] [notice] Accept mutex: pthread (Default: pthread)
> [Thu Oct 31 22:24:51 2002] [alert] Child 736 returned a Fatal error...
> Apache is exiting!
> [Thu Oct 31 22:24:51 2002] [alert] (22)Invalid argument: setuid: unable to change to uid: 65535
> 
> when I run "/usr/sbin/apachectl start" as member of Administrator
> apache starts, but installing the same command as a system service
> won't work.
> 
> the file /var/run/httpd.pid looks like bevore:
> 
> -rw-rw-rw-    1 SYSTEM   SYSTEM          5 Oct 31 22:24 httpd.pid
> 
> Any ideas?

have there been any cerious pthread mutex changes in cygwin 1.3.14? I
haven't been following the list very closely.

BTW, I see from one of my development environments, that apache (even
current 1.3.27) has problems with acceppt serialization for cygwin
1.3.12, .13, .14. 

Basically what happens is the following:

httpd starts and serves some pages. When you put the httpds under
heavy load, then seem to "hang" and the port 80 seems not to be
connectable anymore.

This symtom is not for cygwin 1.3.10. So my question: Has there been
any serious change in socket, accept handling from 1.3.10 up to
1.3.14?

Chris, Corinna?!

Stipe

tolj AT wapme-systems DOT de
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info AT wapme-systems DOT de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are

--
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/

- Raw text -