Red Hat Bugzilla – Bug 77703
Fixed MM semaphore file path prohibits starting up unprivileged apache instances
Last modified: 2007-04-18 12:48:22 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721
Description of problem:
The EAPI MM apache extension, applied as a patch to the pristine Apache HTTP
server sources, contains a fixed path for the semaphore file, pointing to
/var/run/httpd.mm.$pid. If the file cannot be opened, apache refuses to start up.
This fact prohibits starting up a system-installed apache from an unprivileged
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Fire up apache (with an alternative ServerRoot) as any non-root account.
Actual Results: Apache doesn't start, complains:
Ouch! ap_mm_create(1048576, "/var/run/httpd.mm.26391") failed
Error: MM: mm:core: failed to open semaphore file (Permission denied): OS: No
such file or directory
Expected Results: Apache should have started up.
At least two different strategies should be performed:
- using some configuration directive or environment variable to override the
- in case the semaphore file cannot be opened, do not die, but simply do not use
the mm-provied features. This _is_ possible, as demonstrated by the fact that
Apache doesn't contain those features in the first place.
*** Bug 80923 has been marked as a duplicate of this bug. ***
The good fix for this is to make EAPI_MM_CORE_PATH server-root relative; e.g.
add a symlink /etc/httpd/run -> /var/run and use EAPI_MM_CORE_PATH="run/httpd.mm".
*** This bug has been marked as a duplicate of 37233 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.