still not found any solutions, but I found processes became defunct after reloading.
On Wed, Jul 25, 2012 at 3:57 PM, Samuel <[email protected]> wrote: > one of my servers has uwsgi process defunct this afternoon from time to > time. > > uwsgi log said: > > Wed Jul 25 15:51:33 2012 - mapped socket 0 (:8080) to worker 1 > Wed Jul 25 15:51:33 2012 - dup2(): Resource temporarily unavailable > [uwsgi.c line 2950] > Wed Jul 25 15:51:33 2012 - Respawned uWSGI worker 2 (new pid: 15970) > Wed Jul 25 15:51:33 2012 - DAMN ! worker 3 (pid: 15961) died :( trying > respawn ... > Wed Jul 25 15:51:33 2012 - Respawned uWSGI worker 3 (new pid: 15971) > Wed Jul 25 15:51:33 2012 - DAMN ! worker 4 (pid: 15962) died :( trying > respawn ... > Wed Jul 25 15:51:33 2012 - Respawned uWSGI worker 4 (new pid: 15972) > Wed Jul 25 15:51:33 2012 - DAMN ! worker 5 (pid: 15963) died :( trying > respawn ... > Wed Jul 25 15:51:33 2012 - Respawned uWSGI worker 5 (new pid: 15973) > Wed Jul 25 15:51:33 2012 - DAMN ! worker 6 (pid: 15964) died :( trying > respawn ... > Wed Jul 25 15:51:33 2012 - Respawned uWSGI worker 6 (new pid: 15974) > Wed Jul 25 15:51:33 2012 - DAMN ! worker 7 (pid: 15965) died :( trying > respawn ... > Wed Jul 25 15:51:33 2012 - Respawned uWSGI worker 7 (new pid: 15975) > Wed Jul 25 15:51:33 2012 - DAMN ! worker 8 (pid: 15966) died :( trying > respawn ... > Wed Jul 25 15:51:33 2012 - Respawned uWSGI worker 8 (new pid: 15976) > Wed Jul 25 15:51:33 2012 - DAMN ! worker 9 (pid: 15967) died :( trying > respawn ... > Wed Jul 25 15:51:33 2012 - Respawned uWSGI worker 9 (new pid: 15977) > Wed Jul 25 15:51:33 2012 - DAMN ! worker 10 (pid: 15968) died :( trying > respawn ... > Wed Jul 25 15:51:33 2012 - Respawned uWSGI worker 10 (new pid: 15978) > Wed Jul 25 15:51:33 2012 - mapped socket 0 (:8080) to worker 2 > Wed Jul 25 15:51:33 2012 - dup2(): Resource temporarily unavailable > [uwsgi.c line 2950] > Wed Jul 25 15:51:33 2012 - mapped socket 0 (:8080) to worker 3 > Wed Jul 25 15:51:33 2012 - dup2(): Resource temporarily unavailable > [uwsgi.c line 2950] > Wed Jul 25 15:51:33 2012 - mapped socket 0 (:8080) to worker 4 > Wed Jul 25 15:51:33 2012 - dup2(): Resource temporarily unavailable > [uwsgi.c line 2950] > Wed Jul 25 15:51:34 2012 - mapped socket 0 (:8080) to worker 5 > Wed Jul 25 15:51:34 2012 - dup2(): Resource temporarily unavailable > [uwsgi.c line 2950] > Wed Jul 25 15:51:34 2012 - dup2(): Resource temporarily unavailable > [uwsgi.c line 2950] > Wed Jul 25 15:51:34 2012 - dup2(): Resource temporarily unavailable > [uwsgi.c line 2950] > Wed Jul 25 15:51:34 2012 - dup2(): Resource temporarily unavailable > [uwsgi.c line 2950] > Wed Jul 25 15:51:34 2012 - dup2(): Resource temporarily unavailable > [uwsgi.c line 2950] > Wed Jul 25 15:51:34 2012 - dup2(): Resource temporarily unavailable > [uwsgi.c line 2950] > > > > and no way to be gracefully reloaded. > > > I had met such problems before on another server, but the problems > disappeared with an upgraded installation. however, no luck this time. I > have uwsgi 1.2.4 reinstalled twice. > > -- *吴焱红(Samuel)* 博客: blog.shanbay.com 微博: 扇贝网 <http://www.weibo.com/shanbay> 人人网： 一起背单词公共主页 <http://page.renren.com/699128841?ref=lnkprofile>
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
