Hi,

On Fri, 21 Sep 2012 13:12:41 +0200
Łukasz Mierzwa <[email protected]> wrote:

> 2012/9/21 Marcin Deranek <[email protected]>:
> > Worker stays in busy state forever.
> 
> Add --harakiri <seconds>, if it's app issue than You will know where
> it's hanging*.

Unfortunately it doesn't tell me much:

Fri Sep 21 13:40:11 2012 - *** HARAKIRI ON WORKER 4 (pid: 2127) ***
Fri Sep 21 13:40:11 2012 - *** backtrace of 2127 ***
Fri Sep 21 13:40:11 2012 - /usr/sbin/uwsgi(uwsgi_backtrace+0x25) [0x42fe25]
Fri Sep 21 13:40:11 2012 - /usr/sbin/uwsgi(what_i_am_doing+0x19) [0x430309]
Fri Sep 21 13:40:11 2012 - /lib64/libc.so.6 [0x35d42302d0]
Fri Sep 21 13:40:11 2012 - /lib64/libpthread.so.0 [0x35d4a0d4c4]
Fri Sep 21 13:40:11 2012 - /lib64/libpthread.so.0 [0x35d4a08e1a]
Fri Sep 21 13:40:11 2012 - /lib64/libpthread.so.0(pthread_mutex_lock+0x3c) 
[0x35d4a08cdc]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee16770349]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_thread_stop_timer_thread+0x1f) 
[0x2aee16772c8f]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_fork_err+0xdf) [0x2aee166e325f]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee166a5ab5]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee166a611b]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee166a6196]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee1675f2ab]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee1676221d]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee16766b3f]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_vm_invoke_proc+0x2d7) 
[0x2aee16767a47]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee166861ed]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee1675f2ab]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee1676221d]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee16766b3f]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_yield_values+0x5a8) [0x2aee1676eb88]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee16679cb6]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_yield+0x531) [0x2aee1676e191]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_ary_each+0x3c) [0x2aee1665692c]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee16767ff8]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_iterate+0xcb) [0x2aee1675ba2b]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_block_call+0x2b) [0x2aee1675bbdb]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee1667a89d]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee1675f2ab]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee1676221d]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee16766b3f]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_vm_invoke_proc+0x2d7) 
[0x2aee16767a47]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee1675eef9]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee1676221d]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee16766b3f]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_yield+0x252) [0x2aee1676deb2]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee16695947]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee166961b3]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(st_foreach+0xb1) [0x2aee1671a891]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee166987ea]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_ensure+0x77) [0x2aee16680db7]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_hash_foreach+0x36) [0x2aee16697bb6]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee16698131]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee1675f2ab]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee1676221d]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee16766b3f]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee16767ef0]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_class_new_instance+0x32) 
[0x2aee166bfcd2]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee1675f2ab]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee1676221d]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee16766b3f]
Fri Sep 21 13:40:11 2012 - /usr/local/ruby1.9/lib64/libruby.so.1.9 
[0x2aee16767ef0]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_funcall+0x241) [0x2aee1675df41]
Fri Sep 21 13:40:11 2012 - 
/usr/local/ruby1.9/lib64/libruby.so.1.9(rb_protect+0xe2) [0x2aee16680f32]
Fri Sep 21 13:40:11 2012 - 
/usr/lib64/uwsgi/rack_plugin.so(uwsgi_rack_request+0x4e4) [0x2aee1641fa04]
Fri Sep 21 13:40:11 2012 - /usr/sbin/uwsgi(wsgi_req_recv+0xad) [0x40ee9d]
Fri Sep 21 13:40:11 2012 - /usr/sbin/uwsgi(simple_loop+0x16a) [0x42c1aa]
Fri Sep 21 13:40:11 2012 - /usr/sbin/uwsgi(uwsgi_ignition+0x1af) [0x42e2ff]
Fri Sep 21 13:40:11 2012 - /usr/sbin/uwsgi(uwsgi_start+0xf9a) [0x42f2ea]
Fri Sep 21 13:40:11 2012 - /usr/sbin/uwsgi(main+0x96c) [0x4320dc]
Fri Sep 21 13:40:11 2012 - /lib64/libc.so.6(__libc_start_main+0xf4) 
[0x35d421d994]
Fri Sep 21 13:40:11 2012 - /usr/sbin/uwsgi [0x40c239]
Fri Sep 21 13:40:11 2012 - *** end of backtrace ***


> [*] check if Your rack version is affected by
> http://stackoverflow.com/questions/6921398/thin-server-process-hanging-at-100-cpu-in-what-appears-to-be-a-regex-loop-wher,
> upgrade if it's too old

The worker in busy state is completely idle, so it's very unlikely we
are hitting this bugs.
Digging a bit more..

Marcin
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to