Hi, i was unable to test sooner because the site went up when you answer. Now that it went down I add --harakiri-verbose and i fot the following
*** Starting uWSGI 0.9.9.2 (64bit) on [Tue Oct 18 17:46:42 2011] *** compiled with version: 4.5.2 on 27 September 2011 19:38:54 detected binary path: /usr/local/bin/uwsgi your memory page size is 4096 bytes *** WARNING: you have enabled harakiri without post buffering. Slow upload could be rejected on post-unbuffered webservers *** shared area mapped at 0x7f9670600000, you can access it with uwsgi.sharedarea* functions. uwsgi socket 0 bound to TCP address 127.0.0.1:9001 fd 4 Python version: 2.7.1+ (r271:86832, Apr 11 2011, 18:37:12) [GCC 4.5.2] Python main interpreter initialized at 0x24142d0 your server socket listen backlog is limited to 100 connections *** Operational MODE: preforking *** added /opt/web2py/ to pythonpath. WSGI application 0 (mountpoint=) ready on interpreter 0x24142d0 pid: 16069 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 16069) spawned uWSGI worker 1 (pid: 16076, cores: 1) spawned uWSGI worker 2 (pid: 16077, cores: 1) spawned uWSGI worker 3 (pid: 16078, cores: 1) spawned uWSGI worker 4 (pid: 16079, cores: 1) *** HARAKIRI ON WORKER 2 (pid: 16077) *** HARAKIRI: -- syscall> 45 0xb 0x2ecd524 0x10 0x0 0x0 0x0 0x7fffb4588c20 0x7f9670202092 HARAKIRI: -- wchan> sk_wait_data HARAKIRI: --- uWSGI worker 2 (pid: 16077) WAS managing request / since Tue Oct 18 17:46:45 2011 --- DAMN ! worker 2 (pid: 16077) died :( trying respawn ... Respawned uWSGI worker 2 (new pid: 16080) Now I'm using this arguments in /opt/init.d/uwsgi: DAEMON_OPTS="-s 127.0.0.1:9001 -M 4 -t 30 -A 4 -p 4 -d /var/log/uwsgi.log --pythonpath $PYTHONPATH --module $MODULE --harakiri-verbose" where PYTHONPATH=/opt/web2py/ and MODULE=wsgihandler Any thoughts? Francisco Costa http://franciscocosta.com On Wed, Oct 12, 2011 at 20:07, Roberto De Ioris <[email protected]> wrote: > > > Hi! > > We are using nginx 1.1.4 + uWSGI 0.9.9.2 for hosting web2py 1.99.2 on > > Ubuntu > > 11.04 > > > > Everything was running smothly, but a few hours ago, one of our web2py > > apps > > stoped working. > > I've restarted uWSGI but the problem persists. Here is the output of > > uwsgi.log after the restart: > > > > > > *** Starting uWSGI 0.9.9.2 (64bit) on [Wed Oct 12 17:05:06 2011] *** > > compiled with version: 4.5.2 on 27 September 2011 19:38:54 > > detected binary path: /usr/local/bin/uwsgi > > your memory page size is 4096 bytes > > *** WARNING: you have enabled harakiri without post buffering. Slow > > upload > > could be rejected on post-unbuffered webservers *** > > shared area mapped at 0x7f304082a000, you can access it with > > uwsgi.sharedarea* functions. > > uwsgi socket 0 bound to TCP address 127.0.0.1:9001 fd 4 > > Python version: 2.7.1+ (r271:86832, Apr 11 2011, 18:37:12) [GCC 4.5.2] > > Python main interpreter initialized at 0x777250 > > your server socket listen backlog is limited to 100 connections > > *** Operational MODE: preforking *** > > added /opt/web2py/ to pythonpath. > > WSGI application 0 (mountpoint=) ready on interpreter 0x777250 pid: 2614 > > (default app) > > *** uWSGI is running in multiple interpreter mode *** > > spawned uWSGI master process (pid: 2614) > > spawned uWSGI worker 1 (pid: 2621, cores: 1) > > spawned uWSGI worker 2 (pid: 2622, cores: 1) > > spawned uWSGI worker 3 (pid: 2623, cores: 1) > > spawned uWSGI worker 4 (pid: 2624, cores: 1) > > *** HARAKIRI ON WORKER 2 (pid: 2622) *** > > HARAKIRI: --- uWSGI worker 2 (pid: 2622) WAS managing request / since Wed > > Oct 12 17:05:08 2011 --- > > DAMN ! worker 2 (pid: 2622) died :( trying respawn ... > > Respawned uWSGI worker 2 (new pid: 2625) > > > > > > What can I do? > > add --harakiri-verbose in this way you will now why your request became > stuck > > > > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
