Bug 61190 - not all mod_fcgid zombie process are being clean up
Summary: not all mod_fcgid zombie process are being clean up
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_fcgid (show other bugs)
Version: 2.2.32
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2017-06-15 17:40 UTC by Nicolas Marguglio
Modified: 2018-11-07 21:09 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Marguglio 2017-06-15 17:40:45 UTC
I am opening this as I am having the same issue described in:

http://apache-http-server.18135.x6.nabble.com/unreaped-zombie-children-of-mod-fcgid-td5008378.html

But I do not see any follow up or bug reported for it.

In summary, I do have zombie processes being left by mod_fcgid only happening when one of the httpd process crash. Not the process manager httpd process. In my particular case this is happening because httpd is exceeding his "-v" ulimit and grsec kills it.

Regardless, as described on the mail thread a better way to handle this scenario is needed.

One of the solutions described was add these "busy timeout process" to the "error list" but it was mention to have drawbacks.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:22 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.