You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/04/15 21:36:33 UTC

DO NOT REPLY [Bug 8124] New: - mod_ssl fails to get and release semaphore mutex

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8124>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8124

mod_ssl fails to get and release semaphore mutex

           Summary: mod_ssl fails to get and release semaphore mutex
           Product: Apache httpd-2.0
           Version: 2.0.35
          Platform: PC
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_ssl
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: martin.t.kutschker@blackbox.net


On my Linux (RedHat 7.2) mod_ssl logs an error whenever it tries to access a
system v semaphore based mutex. For whatever reason, it does not complain when
creating the mutex. It looks like a permission problem to me (I added error
number reporting to mod_ssl), but I don't know why. Apache itself creates the
shared mem and the semaphores as root and nobody with the permissions set to 600.

After forcing file based locking by hacking(see bug #8122) the errors disappeared.