Strange socket related error with supervisord

05 April 2011 5 comments Linux

This blog post is 7 years old! Most likely, its content is outdated. Especially if it's technical.

This took me a long time to figure out so I thought I'd share.

Basically, I'm a newbie supervisor administrator and I was setting up a new config and I kept getting these errors:

# supervisord -n
2011-04-04 17:25:11,700 CRIT Set uid to user 1000
2011-04-04 17:25:11,700 WARN Included extra file "/etc/supervisor/conf.d/gkc.conf" during parsing
Error: Cannot open an HTTP server: socket.error reported errno.ENOENT (2)
For help, use /usr/local/bin/supervisord -h

The reason was that in my config I had the line:

[unix_http_server]
file=/var/lib/tornado/run/gkc.sock

but the directory /var/lib/tornado/run didn't exist. Creating that solved the problem.

Lesson learned from all this is that when specifying locations of .sock files always make sure the directories exist and that the current user can write to them.

Follow @peterbe on Twitter

Destry 29 August 2011 Reply

This is way bteetr than a brick & mortar establishment.

Anonymous 18 May 2016 Reply

Yea, pretty much making sure that all paths listed in the config file exists and are accessible to your user will fix the error. Thanks dude..

Anonymous 11 January 2018 Reply

Wow, thanks, it works

Anonymous 05 February 2018 Reply

Thanks !!! I got to solve my issue.

Michael Jacob 07 May 2018 Reply

I just ran into the same issue, turned out that /var/run is a tempfs nowadays, so the subfolder for the sock file went away with each reboot...