I am having the same problem. The workaround described by Jon Walsh did
not work for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1131314
Title:
Issuing service uwsgi reload creates zombie
I believe this may be because the init scripts kill using the name
'uwsgi', except when the following variable in /etc/init.d/uwsgi is:
DAEMON=/usr/bin/uwsgi-core (or in my case: uwsgi_python3)
then the processes are not killed during restart (or stop).
I solved this for uwsgi python by
I had this same problem too. I wonder if this is actually a mixture of a
confusing init script message mixed with the quirks about how uwsgi
decided to respond to signals.
This tipped me off:
http://serverfault.com/questions/347819/ubuntu-11-10-with-nginx-and-
uwsgi
So uwsgi has two pidfile
Same problem. I have never used service uwsgi reload, but now I have 8 zombie
uwsgi-core processes after service uwsgi stop.
Debian 6.0.5.
** Also affects: uwsgi (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have to add that even when never using reload, stop also doesn't work
all the time. When letting uwsgi run for a while I thought I'd be safe
not using reload, but stop and start. But after stop there are still
processes running.
service uwsgi start
(let some time pass)
service uwsgi stop
Managing uwsgi daemon with upstart would solve this problem in a more
reliable way, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1131314
Title:
Issuing service uwsgi reload creates zombie
** Branch linked: lp:~lqs/ubuntu/precise/uwsgi/fix-for-1131314
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1131314
Title:
Issuing service uwsgi reload creates zombie uwsgi processes
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: uwsgi (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1131314
Title:
I have the same problem - uwsgi decided to be zombified, and when I
mistakenly decided to reboot the VPS, it got stuck because uwsgi was
still zombified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
