[rabbitmq-discuss] beam blocking
carlhoerberg
carl.hoerberg at gmail.com
Thu May 8 02:36:06 BST 2014
Have a cluster where the nodes sometimes crash on high load, nothing is shown
in the rabbitmq logs, but this shows up in syslog:
kernel: [582840.748073] INFO: task beam:9794 blocked for more than 120
seconds.
kernel: [582840.748082] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
kernel: [582840.748088] beam D ffff8800efc13700 0 9794
9718 0x00000000
kernel: [582840.748092] ffff8800e7bc3cb8 0000000000000282 0000000000000000
ffffffffffffffe0
kernel: [582840.748095] ffff8800e7bc3fd8 ffff8800e7bc3fd8 ffff8800e7bc3fd8
0000000000013700
kernel: [582840.748098] ffff88000249c4d0 ffff88000249ade0 00007f7c2aa289e0
ffff8800024b1180
kernel: [582840.748101] Call Trace:
kernel: [582840.748109] [<ffffffff81659bbf>] schedule+0x3f/0x60
kernel: [582840.748113] [<ffffffff8106c535>] exit_mm+0x85/0x130
kernel: [582840.748116] [<ffffffff8106c74e>] do_exit+0x16e/0x450
kernel: [582840.748120] [<ffffffff8109e4d9>] ?
futex_wait_queue_me+0xc9/0x100
kernel: [582840.748122] [<ffffffff8109e14f>] ? __unqueue_futex+0x3f/0x80
kernel: [582840.748126] [<ffffffff8107ad4a>] ? __dequeue_signal+0x6a/0xb0
kernel: [582840.748128] [<ffffffff8106cbd4>] do_group_exit+0x44/0xa0
kernel: [582840.748131] [<ffffffff8107d8cc>]
get_signal_to_deliver+0x21c/0x420
kernel: [582840.748135] [<ffffffff81014825>] do_signal+0x45/0x130
kernel: [582840.748137] [<ffffffff810a126c>] ? do_futex+0x7c/0x1b0
kernel: [582840.748139] [<ffffffff810a14e2>] ? sys_futex+0x142/0x1a0
kernel: [582840.748142] [<ffffffff81091d7f>] ? __put_cred+0x3f/0x50
kernel: [582840.748144] [<ffffffff81014ad5>] do_notify_resume+0x65/0x80
kernel: [582840.748147] [<ffffffff81664350>] int_signal+0x12/0x17
RabbitMQ 3.3.1, Erlang 17, ubuntu 12.04
--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/beam-blocking-tp35412.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
More information about the rabbitmq-discuss
mailing list