05 April 2011 5 comments Linux
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.
This is way bteetr than a brick & mortar establishment.
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..
Wow, thanks, it works
Thanks !!! I got to solve my issue.
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...