Hi, Can you try this method? here you should mention your webserver user instead of nginx.
[uwsgi] ## appropriate user and permissions uid=nginx gid=nginx chmod-socket=666 chown-socket=nginx:nginx On Fri, Jul 24, 2015 at 12:52 AM, Thiago Farina <[email protected]> wrote: > On Thu, Jul 23, 2015 at 3:16 PM, Roberto De Ioris <[email protected]> > wrote: > > > >> Hi, > >> > >> I'm new to uwsgi, so forgive me if this question was already answered. > >> > >> I tried to find the answer on Google, but it didn't help me much. > >> > >> After rebooting my server, uwsgi is unable to write the socket file > >> into /var/run. > >> > >> $ uwsgi --ini uwsgi.ini > >> ... > >> $ cat /tmp/uwsgi-projectname.log > >> ... > >> thunder lock: disabled (you can enable it with --thunder-lock) > >> bind(): Permission denied [core/socket.c line 230] > >> > >> My uwsgi.ini is like as follow (modified): > >> > >> [uwsgi] > >> daemonize = /tmp/uwsgi-projectname.log > >> pidfile = /tmp/uwsgi-projectname.pid > >> chdir = /path/to/project > >> #http-socket=0.0.0.0:8000 > >> socket=/var/run/uwsgi-project.sock > >> logto=/var/log/uwsgi/%n.log > >> wsgi-file=projectname.py > >> callable=app > >> processes = 2 # number of cores on machine > >> max-requests = 5000 > >> chmod-socket = 666 > >> master = True > >> vacuum = True > >> > >> > > > > hi, try removing the /var/run/uwsgi-project.sock > > > Did that, or actually I think this file was cleaned up automatically > on the boot. Either way, not having it didn't help. > > > very probably it is owner by root for a previous run of the server. > > > > Eventually ensure /var/run is writable by the user running uWSGI > I have tried searching again on Google for this, but haven't found any > satisfactory answer even on stackoverflow. :( > > Do I have to add my user to some privileged group? If yes, what is the > command line for this? > > In case it helps, the following is the groups my user is: > > $ groups tfarina > tfarina : tfarina adm dialout cdrom plugdev netdev lpadmin admin sambashare > > I need a persistent solution, hence chown does not suffice because it > will be reseted in case the system reboots. > > -- > Thiago Farina > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- *Best RegardsManivel Rajendran*
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
