On 14/12/2014, at 7:11 AM, Christiaan Stoudt <[email protected]> wrote:
> WSGIDaemonProcess mydomain_com user=nobody group=nobody display-name=%{GROUP}
> WSGIProcessGroup mydomain_com
> WSGIScriptAlias / /home/mydomain/public_html/d171p275/mydomain_com/wsgi.py
The change I made was to add a 'socket-user' option to WSGIDaemonProcess. You
need to add that option and set it to the user name which the Apache child
worker process would be running as after mod_ruid2 switched the uid. For
example:
WSGIDaemonProcess mydomain_com user=nobody group=nobody display-name=%{GROUP}
socket-user=username
WSGIProcessGroup mydomain_com
WSGIScriptAlias / /home/mydomain/public_html/d171p275/mydomain_com/wsgi.py
If you don't know what mod_ruid2 is setting the uid to for some reason. Pull
down the latest mod_wsgi from github develop branch and use it. I have changed
the logging so it ail show what the Apache child worker process hid was when it
was trying to connect:
[Sun Dec 14 12:25:16 2014] [error] [client ::1] (13)Permission denied: mod_wsgi
(pid=15689): Unable to connect to WSGI daemon process 'xxx' on
'/private/var/run/wsgi.15675.0.1.sock' as user with uid=70.
So if get that error, the socket-user option should specify the user given by
the logged uid.
Graham
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
