From the top of my head and a quick `git grep` later, at least these configuration entries may cause this (the underlying uwsgi C call for that message is “simple_goodbye_cruel_world”, by the way).
· max-requests · max-worker-lifetime · reload-on-as · reload-on-rss Post your configuration? Best, Aarni From: [email protected] [mailto:[email protected]] On Behalf Of Jayadevan Maymala Sent: Tuesday, November 26, 2013 9:59 AM To: [email protected] Subject: [uWSGI] uwsgi killing processes Hell everyone, I have deployed a web2py app in nginx/uwsgi on CentOS box. I keep seeing messages like this in the uwsgi log - "GET /everest3/default/user/logout => generated 67 bytes in 64 msecs (HTTP/1.1 303) 3 headers in 192 bytes (1 switches on core 0) ...The work of process 3666 is done. Seeya! worker 1 killed successfully (pid: 3666) Respawned uWSGI worker 1 (new pid: 3669) " This is an issue when I try to strace a process and find out what is happening. How can I stop this from happening? Why/when do processes get killed like this? Regards, Jayadevan
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
