general/6869: Only constant kill HUPs to Apache temporarily repair a "Resource temporarily unavailable: couldn't spawn child process"

[Bill Webb <ww...@adni.net>]

>Number:         6869
>Category:       general
>Synopsis:       Only constant kill HUPs to Apache temporarily repair a "Resource temporarily  unavailable: couldn't spawn child process"
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun Nov 19 20:10:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     wwebb@adni.net
>Release:        1.3.14
>Organization:
apache
>Environment:
Redhat v7
usename -a: 2.2.16-22 #1 Tue Aug 22 16:16:55 EDT 2000 i586 unknown

Having upgraded Apache, I am now suddendly plagued with the following error messages:
Resource temporarily  unavailable: couldn't spawn child process  (pertains to CGI scripts and it is not a CGI configuration issue).  If I do a kill HUP on Apache, all works well again for a few hours, then the error messages begin again.
I did check daja news and others have reported similiar experiences, however, unless I missed it, no one knows how to fix the problem.  I did upgrade the kernel at the same time I upgraded Apache.  If I screwed-up and this is not an Apache problem--my apologies.

>Description:

Having upgraded Apache, I am now suddendly plagued with the following error messages:
"Resource temporarily  unavailable: couldn't spawn child process"  (pertains to CGI scripts and it is not a CGI configuration issue).  If I do a kill HUP on Apache, all works well again for a few hours, then the error messages begin again.
I did check daja news and others have reported similiar experiences, however, unless I missed it, no one knows how to fix the problem.  I did upgrade the kernel at the same time I upgraded Apache.  If I screwed-up and this is not an Apache problem--my apologies.

>How-To-Repeat:
I don't know.
>Fix:
No.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]