www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <ma...@znep.com>
Subject Re: general/1680: Critically anomalous behavior when upgrading from 1.3a1 to 1.3b3
Date Thu, 15 Jan 1998 23:10:01 GMT
The following reply was made to PR general/1680; it has been noted by GNATS.

From: Marc Slemko <marcs@znep.com>
To: Morgan Davis <mdavis@cts.com>
Cc: Apache bugs database <apbugs@apache.org>
Subject: Re: general/1680: Critically anomalous behavior when upgrading  from 1.3a1 to 1.3b3
Date: Thu, 15 Jan 1998 16:05:48 -0700 (MST)

 On Thu, 15 Jan 1998, Morgan Davis wrote:
 
 > At 02:38 PM 1/15/98 -0700, you wrote:
 > >On 15 Jan 1998, Morgan Davis wrote:
 > >
 > >> Compiled 1.3b3 from official sources with the no2slash patch,
 > >> and compiler options and modules identical to the 1.3a1 previously
 > >> built on the same server (same OS version).  Runs fine while load
 > >> is light.  But under load (approx. 100 virtual hosts taking about
 > >> 700 cumulative hits a minute), the parent and most children will
 > >> suddenly die off, with a single child remaining as a zombie.
 > >> Subsequent attempts to restart httpd fail since Port 80 is already
 > >> bound by the zombie child.  Prior to the collapse, odd behavior is
 > >> noticed, such as references to a particular virtual host end up
 > >> bringing up a totally different virtual host site, or there is a
 > >> failure to connect at all.  A reboot is necessary to get the server
 > >> back up, but will eventually collapse again with exact same state.
 > >> No core file to be found.
 > >
 > >Are you using NFS?
 > 
 > Yes.
 > 
 > The NFS server is on a dedicated, secondary interface, and all the web data
 > comes over this.  The NFS server is hosted on BSDI 2.1 with a DTP RAID
 > configuration.  If this is known to be problematic, we are ready to bring
 > up an external RAID and are considering hosting it on another FreeBSD 2.2.5
 > machine in order take advantage of NFS version 3.  Would you recommend this?
 
 Where is your ServerRoot?  If it is NFS mounted, you should move it to a
 local directory using the LockFile directive (eg. LockFile
 /var/run/accept.lock).
 
 If this isn't the case or don't help, there are a few other things to try.
 

Mime
View raw message