> Den 26/02/2015 kl. 07.56 skrev Kaloian <kaloian.min...@gmail.com>: > > Hi Erik, > > No it doesn't start at all, running the gunicorn_start script gives: > > [ERROR] Retrying in 1 second. > [ERROR] Retrying in 1 second. > [ERROR] Retrying in 1 second. > [ERROR] Retrying in 1 second. > [ERROR] Retrying in 1 second. > [ERROR] Can't connect to /path/to/my/gunicorn.sock > > This is why I thought that the missing sock file is failing it to start. Do > you think it could be something else? > I have already tried to add the absolute path in gunicorn_start but nothing > changed.
A UNIX socket is like a TCP connection, except it's represented as a file. gunicorn is supposed to create it on startup and destroy it on shutdown, and it shouldn't be present when gunicorn is not running. Maybe you tried to create /path/to/my/gunicorn.sock yourself, and the file is now garbage? Try deleting it. Otherwise, another instance of gunicorn may be running already. Try "ps aux | grep gunicorn" or "lsof -U | grep gunicorn" if you're on Linux. Also, the user running gunicorn_start must have access to create files in /path/to/my/ Erik -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/091316F1-9473-4A28-B237-FAA8C371E169%40cederstrand.dk. For more options, visit https://groups.google.com/d/optout.
