I'm running a local vagrant VM, Ubuntu 13.10 with nginx reverse proxying to uwsgi.
sudo /etc/init.d/nginx status
* nginx is running
sudo /etc/init.d/uwsgi status
* which one?
If I take a look at the log file for the wsgi app I can see that uwsgi is running, worker processes have been created etc... so is there a hidden instance of uwsgi running somewhere that's confusing the service restart command?
I installed uwsgi using:
apt-get install uwsgi
Here's the app.ini file:
[uwsgi] plugin = python socket = /run/uwsgi/app/myapp/socket chdir = /var/www/myapp module = project.wsgi:application pidfile = /tmp/myapp-master.pid master = True daemonize = /var/log/uwsgi/myapp.log
184.108.40.206-debian. This has to be a bug, but I don't know if it belongs to the people behind the Ubuntu repository, or to uwsgi.