Apache couldn't spawn child process

Apache couldn't spawn child process

Post by Mario Truye » Tue, 29 Dec 1998 04:00:00



Hi,

by upgrading our webserver and OS (Apache 1.3.3 on Solaris 2.6),
I suddenly got a strange error.
This is what the Apache errorlog says:

(12)Not enough space: couldn't spawn child process:
/customer/ibase002/cgi-bin/Count.cgi

I tracked the error-message down to mod_cgi.c.
The machine has more than enough resources to fork new processes, so
the message confuses me to say the least.
What's more, it happens only now and then, what makes it difficult to
investigate.  By the way, I'm using the suexec mechanism.

I hope someone has seen this problem before (and solved it :-) )

Thx,
mario

 
 
 

Apache couldn't spawn child process

Post by Henrik Nordstro » Thu, 31 Dec 1998 04:00:00


Many operating systems limits how many processes a single user may have
by a kernel parameter called maxuproc or something similar (every OS has
it's own name for it). See the documentation to your OS if it has such a
limit.

---
Henrik Nordstrom


> (12)Not enough space: couldn't spawn child process:
> /customer/ibase002/cgi-bin/Count.cgi

> I tracked the error-message down to mod_cgi.c.
> The machine has more than enough resources to fork new processes, so
> the message confuses me to say the least.


 
 
 

Apache couldn't spawn child process

Post by Martin Fische » Wed, 20 Jan 1999 04:00:00


Facing the same problem w/ Apache 1.3.3 / Win98
any hints are highly welcome!

Martin


> Many operating systems limits how many processes a single user may have
> by a kernel parameter called maxuproc or something similar (every OS has
> it's own name for it). See the documentation to your OS if it has such a
> limit.

> ---
> Henrik Nordstrom


> > (12)Not enough space: couldn't spawn child process:
> > /customer/ibase002/cgi-bin/Count.cgi

> > I tracked the error-message down to mod_cgi.c.
> > The machine has more than enough resources to fork new processes, so
> > the message confuses me to say the least.

 
 
 

Apache couldn't spawn child process

Post by Ryan Sudbur » Thu, 21 Jan 1999 04:00:00


I'm on a virtual server, and my provider is having the same problems.  We've
concluded that it's caused by too many open files - in our case, server logs
are created on the fly for each client.  It takes some time to resolve
visitors' DNS names from IP addresses, and the log files are basically
sitting around waiting for the DNS names to be resolved - all this time
they're kept open.  What we're going to do is create one master log file,
and get a perl script to parse it and distribute it to each client every
evening.  We're pretty sure that'll work...

My server is running Linux Slackware and Apache 1.3.3.

Ryan Sudbury


>Facing the same problem w/ Apache 1.3.3 / Win98
>any hints are highly welcome!

>Martin


>> Many operating systems limits how many processes a single user may have
>> by a kernel parameter called maxuproc or something similar (every OS has
>> it's own name for it). See the documentation to your OS if it has such a
>> limit.

>> ---
>> Henrik Nordstrom


>> > (12)Not enough space: couldn't spawn child process:
>> > /customer/ibase002/cgi-bin/Count.cgi

>> > I tracked the error-message down to mod_cgi.c.
>> > The machine has more than enough resources to fork new processes, so
>> > the message confuses me to say the least.

 
 
 

Apache couldn't spawn child process

Post by Richard Stockt » Thu, 21 Jan 1999 04:00:00



>Facing the same problem w/ Apache 1.3.3 / Win98
>any hints are highly welcome!

>Martin


>> Many operating systems limits how many processes a single user may have
>> by a kernel parameter called maxuproc or something similar (every OS has
>> it's own name for it). See the documentation to your OS if it has such a
>> limit.

>> ---
>> Henrik Nordstrom


>> > (12)Not enough space: couldn't spawn child process:
>> > /customer/ibase002/cgi-bin/Count.cgi

>> > I tracked the error-message down to mod_cgi.c.
>> > The machine has more than enough resources to fork new processes, so
>> > the message confuses me to say the least.

I'm confused too.  I have 2 large (500+ virtual domains each) servers running
Apache on FreeBSD.  I have had to degrade all the way back to 2.1.6 to get one
of them (with only 128 Megs of Ram) to stop giving me those "spawn" messages.  
I also had to disable the spelling module and both the info and status
modules on that server.   This server averages about 550,000 hits per day
(about 4 gigs of throughput.)

On the other server (256Megs) I tried to upgrade from Apache 1.3.3 to 1.3.4
and suddenly it started spitting out the same spawn messages every couple of
seconds.  Went back to 1.3.3 and they went away.  No other changes.
This server averages 400,000 hits per day, 3.5 gigs of throughput.

Another interesting note.  On both servers I actually had to reboot!  (reboot?
on a unix machine? yes, really.)  in order to get the spawn messages to halt.
Could there be a memory management problem in Apache?  Why would there
continue to be problems after I did a "kill -TERM" to the main httpd process?

Both servers are Pentium Pro (one 300Mhz, one 350Mhz) boxes.

If anyone on the Apache team could enlighten me on why these errors are
suddenly cropping up, I would be most appriciative.
TIA.

 - Richard
***************************************************************
Adhost Internet Advertising - Business Web Site Specialists

400 108th Ave. NE, Suite 714         (425) 454-9520 - Voice
Bellevue, WA 98004                   (425) 453-2181 - Fax
                   http://www.adhost.com/
***************************************************************

 
 
 

Apache couldn't spawn child process

Post by Marc Slemk » Thu, 21 Jan 1999 04:00:00



Quote:>I'm on a virtual server, and my provider is having the same problems.  We've
>concluded that it's caused by too many open files - in our case, server logs
>are created on the fly for each client.  It takes some time to resolve
>visitors' DNS names from IP addresses, and the log files are basically
>sitting around waiting for the DNS names to be resolved - all this time
>they're kept open.  What we're going to do is create one master log file,
>and get a perl script to parse it and distribute it to each client every
>evening.  We're pretty sure that'll work...

They are kept open all the time period, so time to do DNS lookups
has nothing to do with it.

Many OSes have file descriptor limits per process and per system, and
many have limits on the number of processes per user and per system.
If those are set too low, there is nothing Apache can do about it; you
have to configure your OS to remove those limits.

 
 
 

Apache couldn't spawn child process

Post by Daniel Mahone » Fri, 22 Jan 1999 04:00:00


I had a similar problem running Apache 1.3.3 under FreeBSD 3.0.  In my case I
reduced MaxClients from 384 to 320, and added "ulimit -n unlimited" to my
apachectl file to increase the max number of processes allowed to exist.  No
more problem!


> Facing the same problem w/ Apache 1.3.3 / Win98
> any hints are highly welcome!

> Martin


> > Many operating systems limits how many processes a single user may have
> > by a kernel parameter called maxuproc or something similar (every OS has
> > it's own name for it). See the documentation to your OS if it has such a
> > limit.

--
--------------------------------------------------------

"There are 2 solutions to every networking problem - the
right one and the easy one.  Microsoft sells the easy ones"

 
 
 

1. Apache and 'couldn't spawn child process'

I'm running Apache 1.3.3 under Linux 2.0.35, and everything is working fine,
except every one in a while I get in my log file:

[Fri Feb 26 16:40:31 1999] [error] [client 24.226.98.184] (11)Try again:
couldn't spawn child process: /script.cgi.

If I go back and do the exact same thing, it works.  Happens about 20% of the
time.  I obviously maxed my number of processes because I have a really busy
site with alot of CGI, but I need to know what to change to fix this.

Anyone?

2. Linux and Nexgen Nx586?

3. Cannot do mlockall? (cdrecord)

4. Why Apache says 'reason: couldn't spawn child process'?

5. XFree86 Matrox Millenium support

6. No such file or directory: couldn't spawn child process: e:/apache/htdocs/test.pl

7. Apache 1.3.3 - "Resource temporarily unavailable: couldn't spawn child process"

8. Couldn't spawn child process - Apache webserver problem on FreeBSD system.

9. Apache: "Couldn't spawn child process" running CGI script

10. "couldn't spawn child process error" on Apache 1.2/IRIX 6.2

11. Apache Q: couldn't spawn child process