I guess the chmoding worked because the default permission there is
700 on the sockets. And because the owner is apache.apache, while my
WSGI processes run as user/group patrick.patrick, trac.trac or another
user/group.

WSGISocketPrefix is not set, so all the sockets end up in /var/run/
httpd.
If I do "chown root.apache /var/run/httpd" then I get 503 errors
again :(
This also happens when I chmod it to 2750.

I also tried "chmod 2775 /var/run/httpd", but that doesn't work
either. The sockets still have the permission 700...

Regards, PatrickB

On Feb 7, 1:42 pm, Clodoaldo Neto <[email protected]> wrote:
> 2010/2/7 PatrickB <[email protected]>
>
>
>
>
>
> > Hello,
>
> > I'm using mod_wsgi to host a few Django sites, a few Trac sites and
> > some Mercurial repositories. I recently moved from one big mod_wsgi
> > interpreter to a few interpreters by using WSGIDaemonProcess. This was
> > working semi-fine, since I forgot to assign directories to the daemon
> > processes. I did that now, and I got a load of error messages in all
> > the logs. The error messages where something like this:
>
> > [Sun Feb 07 13:00:55 2010] [error] [client 65.55.106.162]
> > (13)Permission denied: mod_wsgi (pid=19109): Unable to connect to WSGI
> > daemon process 'patrickbregman.eu' on '/var/run/wsgi.19074.0.2.sock'
> > after multiple attempts.
>
> > I "fixed" this by doing a "chmod 777 /var/run/httpd/wsgi.* ", which
> > seems to work. For now. Is there a better solution known, or should I
> > just modify my Apache initscript to do this for me every time? Not a
> > big problem for me, but it isn't a very nice solution in my opninion.
>
> If mod_wsgi was trying to connect to /var/run/wsgi.#.sock then how chmoding
> /var/run/httpd/wsgi.* worked?
>
> What is the value of the WSGISocketPrefix directive?
>
> You can try to chown root.apache the /var/run/httpd directory and then chmod
> it to 2750.
>
> Regards, Clodoaldo
>
>
>
> > Thanks in advance,
> > PatrickB
>
> > --
> > You received this message because you are subscribed to the Google Groups
> "modwsgi" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
>
> [email protected]<modwsgi%[email protected] >
> .> For more options, visit this group at
>
> http://groups.google.com/group/modwsgi?hl=en.
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en.

Reply via email to