I'm running Supervisord on my Ubuntu 14.04 server and everything works fine. I deploy using a git push and upon deployment I also need to restart my application server (gunicorn) which I can supposedly do using supervisorctl.

un my supervisord.conf, gunicorn is defined as follows:

command=/home/imb/imb/venv/bin/gunicorn --worker-class eventlet -b -w 1 app:app

and I enabled supervisorctl like this:

serverurl=unix:///var/run/supervisor.sock ; use a unix:// URL  for a unix socket

I started supervisor using

sudo supervisord -c /home/imb/imb/supervisord.conf

As far as I understand I now should be able to restart gunicorn using the command supervisorctl restart gunicorn, but when I do that I get

$ supervisorctl restart gunicorn
unix:///var/run/supervisor.sock no such file

I checked and the file /var/run/supervisor.sock indeed doesn't exist, even though I'm sure supervisor is in fact running:

$ ps -A | grep supervisor
27211 ?        00:00:00 supervisord

Does anybody know why the /var/run/supervisor.sock file isn't created, even though supervisor is clearly running? All tips are welcome!


Alright, after messing around some more I found what I did wrong.

Turns out the lines for supervisorctl below, only tell supervisorctl where it can find the socket file.


Further above in the file there are two other lines which define where the file is actually created:


As you can see that created the socket file in /tmp/ while supervisorctl tried to read it from /var/run/. I changed the last line to file=/var/run/supervisor.sock and now it works beatifully.

I hope this answer might help someone else dealing with the same trouble.

Also, you can check out the link provided by @MariusMatutiae in the comments: https://stackoverflow.com/questions/10716159/nginx-and-supervisor-setup-in-ubuntu

  • 1
    I see that the page I suggested did contain the right solution for you, stackoverflow.com/a/28469044/2796243 . I am glad to see I could help, cheers. – MariusMatutiae May 5 '16 at 6:35
  • @MariusMatutiae - Yes indeed, I might not have given you the recognition which you deserved. So a big thanks to you! Note that I'm still happy to give you the 50 bounty points. Just write an answer and I'll reward it to you.. :-) – kramer65 May 5 '16 at 8:54
  • Thanks, very nice of you, but I did not really find the solution. It's just that the page above contains several different solutions, only one of which (happily) applies to you, but it can be helpful to others reading this post to know that other solutions may be available, should the need arise. That's all. Cheers. – MariusMatutiae May 5 '16 at 10:48
  • I faced another "funny" problem. Don't use tmp folder for socket file as it's cleaned automatically and socket file will be erased till next supervisord restart. – StalkAlex Jan 6 '17 at 9:25

For users who have the same entry for both




follow below steps to fix the problem -

  1. Delete .sock file from /tmp
  2. Run 'supervisord' command. This will recreate the sock file.
  3. Run 'supervisorctl -i' to check the status of the services.

Hope this helps you!


Upgrade it to MacOS Sierra 10.12.5.

I faced the same issue and everything was right in the config file as well. Later I figured that I had moved to latest MacOS Sierra 10.12.3 and then it didn't work. It had been working on the older version but not at this specific version of MacOS. Then I upgraded it to MacOS Sierra 10.12.5 and everything seems to be working fine.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.