DO NOT REPLY [Bug 7921] - perchild: apr_proc_mutex_[un]lock failed...

2003-03-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
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=7921

perchild: apr_proc_mutex_[un]lock failed...





--- Additional Comments From [EMAIL PROTECTED]  2003-03-21 21:13 ---
Ok, I had a bad morning this day.
My distribution set up the default permissions unaccessible on /, that's why
that error occured.
perchild principally works fine now with "AcceptMutex fcntl", but the processes
are somewaht irritating. I get only one root-process in "top", but three with
"ps -ax", where I cant see the owners. But it should only be wo, as NumServers
is set to 1. I guess the default non-virtual host is still running senselessly? 
:(
I'll try playing around, but it works fine as it should and I'm happy. :)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7921] - perchild: apr_proc_mutex_[un]lock failed...

2003-03-20 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
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=7921

perchild: apr_proc_mutex_[un]lock failed...





--- Additional Comments From [EMAIL PROTECTED]  2003-03-20 08:48 ---
Hi!

I'm afraid the switch to "fcntl" didn't solve my problem. When I had "default"
it tried at least to start the child with the correct uid/gid, now it starts 4
apache processes as root, and one of them tries to handle my request to the
virtual host. It's somewhat weired, as I get a "permission denied" then...

The vhost is this:
>

DocumentRoot /home/kiw/htdocs
ServerName mydomain.tld
ServerPath /home/kiw/htdocs
ScriptAlias /cgi-bin/ /home/kiw/htdocs/cgi-bin/
AssignUserID kiw users
ErrorLog /var/log/apache2/kiw-error_log
CustomLog /var/log/apache2/kiw-access_log combined

<

And the section from the main conf-file is this:
>

NumServers   1
StartThreads 2
MinSpareThreads  1
MaxSpareThreads  4
MaxThreadsPerChild  10
MaxRequestsPerChild  0
AcceptMutex default
ChildPerUserID kiw users 1

<

Platform is Linux on x86, Apache is 2.0.44.
It obviously starts up fine, but I don't get a process with the appropriate
uid/gid and a permission denied when trying to access the website:
>
[Thu Mar 20 09:42:51 2003] [error] [client 217.84.193.150] client denied by
server configuration: /home/kiw/htdocs/
<

The directory is world-readable/-accessible.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7921] - perchild: apr_proc_mutex_[un]lock failed...

2003-02-06 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
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=7921

perchild: apr_proc_mutex_[un]lock failed...

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7921] - perchild: apr_proc_mutex_[un]lock failed...

2002-07-02 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
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=7921

perchild: apr_proc_mutex_[un]lock failed...





--- Additional Comments From [EMAIL PROTECTED]  2002-07-02 21:53 ---
*** Bug 8904 has been marked as a duplicate of this bug. ***

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7921] - perchild: apr_proc_mutex_[un]lock failed...

2002-07-02 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
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=7921

perchild: apr_proc_mutex_[un]lock failed...

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||bugs@httpd.apache.org
 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2002-07-02 19:59 ---
You are trying to use SYS V Semaphores for your locking, but that can't work
with perchild.  The docs are not clear about this, because I just found the
problem earlier this week.  Basically, for all of the other MPMs, we create the
semaphore and then change the permissions on the semaphore so that the child
processes can attach to it.  That works for the other MPMs, because they have a
sinlge uid/gid for all of the child processes.  Perchild doesn't have that, it
has multiple uid/gid combinations, so we would have to make the permissions very
lax in order to allow all of the uid/gid's to bind to the semaphore.  Rather
than open the security that much, it is much better to just use a fcntl locking
mechanism.

This can be accomplished by adding:

AcceptMutex fcntl

to your config file.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7921] - perchild: apr_proc_mutex_[un]lock failed...

2002-05-22 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
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=7921

perchild: apr_proc_mutex_[un]lock failed...

[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|apr_proc_mutex_[un]lock |perchild:
   |failed...   |apr_proc_mutex_[un]lock
   ||failed...

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]