Django：使用mod_wsgi创建的SOCK文件的权限错误

Question

I have a Django app running on my server using Apache2 and mod_wsgi. I also having WSGI running in daemon mode. Due to this, I have a small issue that occurs every time I restart my apache2 service.

A new sock file is created in /var/run/ which isn't the issue itself, but due to this, the new file is being created by root and given the owner www-data, my user who is serving the files is not the owner.

My Question :

How do I make it so that the new sock file being created is created with user as the owner and www-data as the group?

Answer 1

As per @GrahamDumpleton 's help, I was able to solve this issue.

Problem

Using the wrong wsgi install ( libapache2-mod-wsgi ) which caused issues when trying to run WSGIDaemonMode inside my apache conf file. I was unable to use the socket-user=user option so that I did not receive a Permission denied problem when a new sock file was created upon service restart.

Solution

For me, I did a fresh install of Debian 8 on my server since I was messing around a lot in my files trying to solve the issue, so I felt this was for the best. Upon a fresh install, using pip install mod_wsgi was able to work ( would not work before my fresh install, even after installing python 2.7.13 ) -- weird, I know...

Since I had mod_wsgi installed properly, I was able to use the socket-user=user option to solve my problem.

Documentation for mod_wsgi