I read the log, and yes, I had a lot of information: Fri Apr 13 17:29:06 2012 - DAMN ! worker 1 (pid: 9871) died :( trying > respawn ... > Fri Apr 13 17:29:06 2012 - Respawned uWSGI worker 1 (new pid: 9881) > Fri Apr 13 17:29:06 2012 - DAMN ! worker 2 (pid: 9872) died :( trying > respawn ... > Fri Apr 13 17:29:06 2012 - worker respawning too fast !!! i have to sleep > a bit (2 seconds)... > Fri Apr 13 17:29:06 2012 - mapped socket 0 (:8080) to worker 1 > Fri Apr 13 17:29:06 2012 - dup2(): Resource temporarily unavailable > [uwsgi.c line 2821] >
so why did it happen so quickly and no way to respawn a new worker? On Fri, Apr 13, 2012 at 5:23 PM, Samuel <[email protected]> wrote: > Thanks for your helps. > > my version is 0.9.9.2 > > pidfile=uwsgi.pid > >> touch-reload=uwsgi.pid >> >> then >> >> $ touch uwsgi.pid >> >> > > so touch-reload and pidfile should be the same file. > > I thought touch-reload can be any file, and I just had a try to see if set > touch-reload file as pid file, but no luck. I also tried on version 1.1.12, > but the result is the same defunct status. > > I meant defunct as the follow line if I executed ps -ef |grep -i uwsgi > > samuel 7751 7750 0 17:20 ? 00:00:00 [uwsgi] <defunct> > > please let me know if more info needed. > > thanks > -- *吴焱红(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
