Solved

Apache-can't spawn child process

Posted on 2000-03-28
3
1,022 Views
Last Modified: 2013-12-24
We are using Apache 1.3 and have these values set:

MaxClients 100
MaxRequestsPerChild 20

Yesterday, a user must have been leaning against the enter key and created over 200 processes causing the web server user 'nobody' to reach its max process limit and start giving the error 'can't spawn child' to new requests. What settings can I use to prevent this from occurring. Is there a setting that will just lock out the offender and not affect anyone else? I believe our AIX is set to allow 300, but read that httpd.h allows 256.
0
Comment
Question by:srollins
  • 2
3 Comments
 

Accepted Solution

by:
triliji earned 100 total points
ID: 2707707
It sounds to me as though the server is doing it's job by not allowing any more child processes to be spawned. I am confused by the statement, "leaned against the enter key" as I don't think this would cause a server to be flooded with PUT commands. I have never heard of this problem and admit that I am unsure of this.
In any event, this would be a rare occurence and the sysadmin should be able to catch these errant mistakes or overloads and kill the processes to free up resources.

The CGI script  can also be modified to limit the number of PUT requests to handle this problem.

Hope this helps
0
 

Author Comment

by:srollins
ID: 2708867
The "leaning again the enter key" causes the form on the screen to be submitted repeatedly because a carriage-return submits the form. Someone leaning on it would continuously submit the form over and over.

You say that I should be able to catch these errant overloads and kill some processes. How do I catch these overloads and how do I know which processes to kill. I don't want to kill a legitimate process that may be writing to the database.
0
 

Expert Comment

by:triliji
ID: 2709063
What O/S are you using?
Do you presently have a program to monitor your sites
activity?

Is the form writing to a binary database or flatfile?
Killing a process can be pinpoint or shotgun
and it should not be hard to detect a runaway process.
Unless your site is receiving millions of hits you should
be able to notice an extraordinary increase in processes being
run.

You can use the kill pid for pinpoint or the
killall for shotgun but be careful not to run it
as root if you are the sysadmin or you could
cause some irreversible damage.

Is this a CGI script you are running?
0

Featured Post

Networking for the Cloud Era

Join Microsoft and Riverbed for a discussion and demonstration of enhancements to SteelConnect:
-One-click orchestration and cloud connectivity in Azure environments
-Tight integration of SD-WAN and WAN optimization capabilities
-Scalability and resiliency equal to a data center

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

If your business is like most, chances are you still need to maintain a fax infrastructure for your staff. It’s hard to believe that a communication technology that was thriving in the mid-80s could still be an essential part of your team’s modern I…
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question