Related

Ubuntu PHPMyAdmin on 14.04 default login details Question Question
Accessing my droplet from my local machine Question Question

Question

Problem with deploying a mezzanine project to VPS

Posted March 13, 2016 2.2k views
Deployment

I am trying to deploy a mezzanine instance to my droplet after following the available tutorials and articles available on this site and the Mezzanine docs.
I am trying to use nginx with gunicorn along with the mezzanine setup.
Everything seems to go well and I deployed using the included fabfile.py
However, whenever I run the site, I get the following errors

2016/03/13 05:52:46 [crit] 4516#0: *2 connect() to unix:/home/oilwatch/mezzanine/oilwatch/gunicorn.sock failed (2: No such file or directory) while connecting to upstream, client: 197.78.155.21, server: 45.55.150.38, request: "GET / HTTP/1.1", upstream: "http://unix:/home/oilwatch/mezzanine/oilwatch/gunicorn.sock:/", host: "45.55.150.38"

I’ve googled around to find a solution but nothing comes close. Has anyone else encountered this and got a solution? I dont know what else to do.

Add a comment
jomeakpoduado
By:
jomeakpoduado

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer
BrookDO June 22, 2016

That error likely means that Gunicorn isn’t running, and the sock file needed for connection is thus not being created. You’ll likely find the cause in the Gunicorn logs, which you need to set by running Gunicorn with a log file directive like so:

gunicorn -b 0.0.0.0:8069 --access-logfile /var/log/yourapp/gunicorn-access.log --error-logfile /var/log/yourapp/gunicorn-error.log

This will give you even more information about setting log levels: http://docs.gunicorn.org/en/develop/configure.html#logging

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help