Activity log for bug #1131314

Date Who What changed Old value New value Message
2013-02-21 17:51:00 Braden MacDonald bug added bug
2013-02-21 17:53:34 Braden MacDonald description I'm using uwsgi, uwsgi-core, and uwsgi-plugin-python (all are version 1.0.3+dfsg-1ubuntu0.1 ) on Ubuntu 12.04.2 LTS, and I've found that although the "service uwsgi start" and "service uwsgi stop" commands work fine, if I issue a "service uwsgi reload" command, it will create zombie "uwsgi-core" processes that do not die with "service uwsgi stop" and can only be killed with SIGKILL ("killall -s 9 uwsgi-core"). Steps to reproduce: apt-get install uwsgi uwsgi-plugin-python # Set up at least one uwsgi python app service uwsgi start service uwsgi reload service uwsgi stop Expected result: No uwsgi processes running. Actual result: several uwsgi-core processes/threads remain running and can only be stopped with SIGKILL. Other reports: Another user asked about this same problem at http://askubuntu.com/questions/211036/cant-repeatedly-reload-uwsgi . That user suggests that the problem is because "after the first reload the process names change from uwsgi to uwsgi-core, and the reload script looks for 'uwsgi' processes with specific pids." I'm using uwsgi, uwsgi-core, and uwsgi-plugin-python (all are version 1.0.3+dfsg-1ubuntu0.1 ) on Ubuntu 12.04.2 LTS, and I've found that although the "service uwsgi start" and "service uwsgi stop" commands work fine, if I issue a "service uwsgi reload" command, it will create zombie "uwsgi-core" processes that do not die with "service uwsgi stop" and can only be killed with SIGKILL ("killall -s 9 uwsgi-core"). Steps to reproduce: apt-get install uwsgi uwsgi-plugin-python # Set up at least one uwsgi python app service uwsgi start service uwsgi reload service uwsgi stop Expected result: No uwsgi processes running. Actual result: several uwsgi-core processes remain running and can only be stopped with SIGKILL. Other reports: Another user asked about this same problem at http://askubuntu.com/questions/211036/cant-repeatedly-reload-uwsgi . That user suggests that the problem is because "after the first reload the process names change from uwsgi to uwsgi-core, and the reload script looks for 'uwsgi' processes with specific pids."
2013-02-25 00:23:46 Launchpad Janitor uwsgi (Ubuntu): status New Confirmed
2013-03-08 05:15:56 Launchpad Janitor branch linked lp:~lqs/ubuntu/precise/uwsgi/fix-for-1131314
2013-03-08 05:29:13 Qishuai Liu bug added subscriber Liu Qishuai
2013-03-15 16:16:51 Sergey Shepelev bug added subscriber Sergey Shepelev
2013-07-26 13:20:36 Vladimir Dmitriev bug added subscriber Vladimir Dmitriev
2013-09-09 10:06:45 vdemin bug added subscriber vdemin
2013-11-10 08:26:35 Dem0n3D bug task added uwsgi (Debian)
2014-07-18 18:42:06 Paul Kilgo attachment added pidfile.log https://bugs.launchpad.net/ubuntu/+source/uwsgi/+bug/1131314/+attachment/4156002/+files/pidfile.log
2015-03-16 04:43:58 Jon Walsh bug added subscriber Jon Walsh