This blog post is 9 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.
- Previous:
- Google's new Page Speed Online hard to beat 04 April 2011
- Next:
- TornadoGists.org - launched and ready! 06 April 2011
- Related by category:
- How to create-react-app with Docker 17 November 2017 Linux
-
Be very careful with your add_header in Nginx! You might make your site insecure 11 February 2018 Linux
- Linux tip: du --max-depth=1 27 September 2007 Linux
- set -ex - The most useful bash trick of the year 31 August 2014 Linux
- Run something forever in bash until you want to stop it 13 February 2018 Linux
- Related by keyword:
- uwsgi weirdness with --http 19 September 2019
- My tricks for using AsyncHTTPClient in Tornado 13 October 2010
- All my apps are now running on one EC2 server 03 November 2013
- Slides about Kwissle from yesterdays London Python Dojo 08 July 2011
- Welcome to the world: DoneCal.com 22 November 2010
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...
You are my hero.
> Mind that age!
> This blog post is 9 years old! Most likely, its content is outdated. Especially if it's technical.
This post is way more useful than the terrible message error.
Error: Cannot open an HTTP server: socket.error reported errno.ENOENT (2)
Thanks!