httpd 2.0.53 processes don't die

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: users@xxxxxxxxxxxxxxxx
Subject: httpd 2.0.53 processes don't die
From: "gdwfkd@xxxxxxxxx" <gdwfkd@xxxxxxxxx>
Date: Wed, 27 Dec 2006 07:57:38 -0800
Delivered-to: mailing list users@xxxxxxxxxxxxxxxx
Mailing-list: contact users-help@xxxxxxxxxxxxxxxx; run by ezmlm
Reply-to: users@xxxxxxxxxxxxxxxx

Running apache 2.0.53 on Solaris 8. Child processes build up to the maximum (MaxClients), and then the web server stops responding so I have to go and kill old httpd process (I never have to restart apache). The processes I kill are generally a few days old, or several hours old.

As I understand it, the server becomes unresponsive when it hits the 200 MaxClients limit, but the KeepAliveTimeout, or at least the Timeout value, should have returned those older processes to general service. This doesn't appear to be happening as I have old httpd processes that just hang around.

Some relevant httpd.conf entries:

Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 15
StartServers         12
MinSpareServers      10
MaxSpareServers      30
MaxClients           200

Thoughts?

Follow-Ups:
- Re: httpd 2.0.53 processes don't die
  - From: Joshua Slive

Prev by Date: passwords on version 2.2.3 for windows XP
Next by Date: ErrorDocument directive for 500 errors not displaying full content
Previous by thread: passwords on version 2.2.3 for windows XP
Next by thread: Re: httpd 2.0.53 processes don't die
Index(es):
- Date
- Thread

[Index of Archives] [Open SSH Users] [Linux ACPI] [Linux Kernel] [Linux Laptop] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Squid] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper]