42👍
for me the way to kill uwsgi instances in a bruteforce manner was:
sudo pkill -f uwsgi -9
21👍
Add a pidfile to your command:
uwsgi --plugins=python --chdir=/var/www/prjt/src/ --socket=127.0.0.1:8889 --module=prjt.wsgi:application --pidfile /tmp/myapp.pid
Then use
uwsgi --stop /tmp/myapp.pid
to stop the uwsgi instance in a safe way.
If you didn’t specify a pidfile when you started the first instance, you can kill it brutally using
kill `pidof uwsgi`
- How to pass data between django views
- Multiple Forms and Formsets in CreateView
- Adding errors to Django form errors.__all__
- How to use Datepicker in django
10👍
you can get the pid of the uwsgi process here lsof -t -i tcp:8000
and kill it then kill -9 pid
- In Django ORM, "values" and "annotate" are not working to group by
- Use a django built in filter in code (outside of a template)
- Django – filtering by "certain value or None"
- How do you divide your project into applications in Django?
3👍
I stop my uwsgi instance by command:
kill -INT `cat ${APP_ROOT}/run/uwsgi.pid`
This command sends signal to uwsgi which cause it to stop.
If you do not know PID than you may:
killall -s INT /ve/path/bin/uwsgi
-1👍
Simliary, I had that issue too.
And I tried all the way(answer) that written in this page.
BUT Nothing was changed.
So I just restart the computer and the problem is gone!!!!!!!!!!!!
Try it!
Source:stackexchange.com