On Wednesday, February 19, 2014 6:21:44 AM UTC+11, Alex Chumbley wrote: > > I have used Ansible to set up a hosted flask app on EC2 as described > here<http://mattupstate.com/python/devops/2012/08/07/flask-wsgi-application-deployment-with-ubuntu-ansible-nginx-supervisor-and-uwsgi.html>. > > However, I'm getting errors like > > 2014/02/18 19:14:56 [error] 31891#0: *8 connect() to unix:/tmp/pile.sock > failed (111: Connection refused) while connecting to upstream, client: > xxx.xxx.xxx.xxx, server: localhost, request: "GET /HTTP/1.1", upstream: > "uwsgi ://unix:/tmp/pile.sock:", host: " > ec2-xx-xxx-xx-xxx.compute-1.amazonaws.com" > > > Or > > > 2014/02/18 19:07:20 [error] 31891#0: *1 connect() to unix:/tmp/pile.sock > failed (111: Connection refused) while connecting to upstream, client: > xxx.xxx.xxx.xxx, server: localhost, request: "GET / HTTP/1.1", upstream: > "uwsgi ://unix:/tmp/pile.sock:", host: " > ec2-xx-xxx-xx-xxx.compute-1.amazonaws.com" > > > I'm guessing it's an issue with uwsgi, but there are no configuration > files for it. I really want to keep ansible fully and let it do it's thing. > Is anyone familiar with this issue? >
So the particular tutorial you used doesn't actually use config files for uwsgi directly - it passes all the parameters to uwsgi in the supervisord configuration. See this template file from the repo for that tut: https://github.com/mattupstate/ansible-tutorial/blob/master/devops/templates/supervisor.ini Judging from your log snippet, to see what configuration uwsgi is actually being started with, you should be able to look at /etc/supervisor/pile.ini ~Justin -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
