I ran into a problem similar to this...
As it turned out it was due to a commo problem between my web server and a
remote database - specifically, the database was being used for access
control. When the commo link between apache and MySQL crapped out apache
sat there spun its wheels and then refused further connections...
MySQL, on the other hand, acted fine - it accepted connections and
performed like it was designed to. I found this out because I wrote a
perl script that tested connections from each server, e.g. apache =>
MySQL, MySQL => MySQL...
Hope this helps...
Perrin Harkins <[EMAIL PROTECTED]> wrote:
> On Tue, 16 Jan 2001, Honza Pazdziora wrote:
> > The machines are alright memorywise, they seem to be a bit slow on
> > CPU, however what bothers me is the deadlock situation to which they
> > get. No more slow crunching, they just stop accepting connections.
>
> I've only seen that happen when something was hanging them up, like
> running out of memory or waiting for a database resource. Are you using
> NFS by any chance?
>
> > Is there a way to allow a lot of children to be spawned but limit
> > the number of children that serve requests?
>
> I don't think you want that. If the server is busy, Apache will spawn
> more as soon as it can. Of course PerlRunOnce is a huge
> liability. Getting rid of that would surely help a lot.
>
> - Perrin
===========================================================================
"If you put three drops of poison into a 100 percent pure Java, you get -
Windows. If you put a few drops of Java into Windows, you still have
Windows."
-- Sun Microsystems CEO, Scott McNealy
____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at
http://home.netscape.com/webmail
