Bug 50873 - httpd does not start properly when built from source with "with-mpm=worker" and ChrootDir directive
Summary: httpd does not start properly when built from source with "with-mpm=worker" a...
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mpm_worker (show other bugs)
Version: 2.2.17
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2011-03-04 18:07 UTC by marcin gajowniczek
Modified: 2018-11-07 21:09 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description marcin gajowniczek 2011-03-04 18:07:07 UTC
I built apache 2.2.17 [ubuntu 10.04] from source with intent to use:

- MPM "worker" instead of "prefork", I used configure switches: --with-mpm=worker and --disable-prefork  

- apache built-in ChrootDir directive

After starting the httpd it seems the parent process starts ok but has problem to create the child processes. The child processes are in [httpd] <defunct> state, they go down and up, httpd does not serve any requests.

I observed also the following:
- When built apache with MPM prefork and used ChrootDir it works OK, all child processes operate OK in jail. Parent process is operating out of jail.
- When build apache with MPM worker and did not use ChrootDir it works OK as well, the same way as with MPM prefork and ChrootDir

Comment 1 William A. Rowe Jr. 2018-11-07 21:09:45 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.