On the following Debian box: Linux hostname 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux
I am running the 2.0.9 version of uwsgi (installed via pip). The relevant portion of my ini file is: single-interpreter = true lazy-apps = true maxrequests = 200 reload-on-as = 256 max-worker-lifetime = 3600 At Wed Mar 4 13:57:54 UTC 2015, I took a look at the uwsgi processes that were running: www-data 16852 16569 0 Mar03 ? 00:00:02 /usr/local/bin/uwsgi --ini redacted.ini www-data 16987 16569 0 Mar03 ? 00:00:01 /usr/local/bin/uwsgi --ini redacted.ini www-data 17053 16569 0 Mar03 ? 00:00:02 /usr/local/bin/uwsgi --ini redacted.ini www-data 17226 16569 0 Mar03 ? 00:00:01 /usr/local/bin/uwsgi --ini redacted.ini www-data 18557 16569 0 02:59 ? 00:00:01 /usr/local/bin/uwsgi --ini redacted.ini www-data 19199 16569 0 04:33 ? 00:00:02 /usr/local/bin/uwsgi --ini redacted.ini www-data 19443 16569 0 05:24 ? 00:00:01 /usr/local/bin/uwsgi --ini redacted.ini www-data 20022 16569 0 07:05 ? 00:00:01 /usr/local/bin/uwsgi --ini redacted.ini www-data 21240 16569 0 10:26 ? 00:00:08 /usr/local/bin/uwsgi --ini redacted.ini www-data 21951 16569 0 13:15 ? 00:00:04 /usr/local/bin/uwsgi --ini redacted.ini Processes 16852 16987 17053 17053 were no longer responding to the front end nginx server; it connects to them, hangs for some number of seconds, then returns a 404. I would have expected those processes to have been killed hours ago as they are well outside the 3600 second configuration for max-worker-lifetime. Is there some reason why they are still hanging around? tx
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
