Hi, there are no files in '/var/log/uwsgi' and "journalctl /usr/local/bin/uwsgi" reports "No journal files were found."
On Wednesday, November 23, 2016 at 1:14:00 PM UTC, Niphlod wrote: > okay, you can see in the first line that /tmp/web2py.socket is mentioned. > > if uwsgi is running, need to check the log to see if any errors comes up > > check in /var/log/uwsgi and/or see if systemd logging reports something > with "journalctl /usr/local/bin/uwsgi" > > On Wednesday, November 23, 2016 at 1:36:35 PM UTC+1, Richard Brown wrote: >> >> Thanks, the answer is 'yes' to all of these checks - web2py.ini file >> attached. I did find out how to see if the uwsgi process is running and it >> does appear to be: >> >> $ ps aux | grep "uwsgi" >> richard 1044 0.0 0.1 4276 1824 pts/0 S+ 10:54 0:00 grep >> --color=auto uwsgi >> >> >> >> On Wednesday, November 23, 2016 at 11:54:21 AM UTC, Niphlod wrote: >> >>> ok, let's break it down. >>> The script basically does: >>> - install and configure nginx >>> - install and configure uwsgi >>> >>> uwsgi is the process that takes care of executing any python code >>> (meaning, your webapp) . >>> nginx is the process that takes care of receiving an http request, >>> passing it down to uwsgi, get the results and send the http response back >>> to your browser. >>> Both need to be running in order for your app to work. >>> >>> In order to let the two communicate, nginx expects a "file" >>> (/tmp/web2py.socket) . That file is created by uwsgi. >>> It's possible that one of the steps of the script didn't work out, hence >>> your error. >>> The error you posted seems to point out that nginx is configured >>> correctly, but for some reason uwsgi is not. >>> >>> The first thing to check is that you have the uwsgi daemon. >>> There's a command, "which", that will tell you the location of any >>> executable is ready on your system. >>> So, type "which uwsgi" in a terminal to know if at least it got >>> installed. it should reply "/usr/local/bin/uwsgi" >>> >>> If it's installed, the next check is see if it's configured correctly. >>> Systemd is used to let uwsgi start: >>> - Check if you have a file at /etc/systemd/system/emperor.uwsgi.service >>> An ini file is responsible to let uwsgi know WHAT to run: >>> - Check if you have a file at /etc/uwsgi/web2py.ini >>> >>> If all of the above checks out, we'll need further steps, but for the >>> time being check them >>> >>> >>> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
