> 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

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


-- 
Roberto De Ioris
http://unbit.com
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to