[rabbitmq-users] v3.3.4 -- meaning of 'brutal_kill' in sasl.log

[Tony]

We occasionally see these in our RabbitMQ server v3.3.4 on Windows SASL.log
file. Are they significant? What do they indicate? They seem to come in
two varieties "Reason: shutdown" and "Reason: badarg...".


=SUPERVISOR REPORT==== 30-Jul-2015::16:38:18 === Supervisor: {<0.6233.229>,
amqp_channel_sup_sup} Context: shutdown_error Reason: shutdown Offender: [{
nb_children,1}, {name,channel_sup}, {mfargs, {amqp_channel_sup,start_link, [
direct,<0.6147.229>, <<"<***@SERVERNAME03.1.6147.229>">>]}}, {restart_
type,temporary}, {shutdown,brutal_kill}, {child_type,supervisor}]


=SUPERVISOR REPORT==== 30-Jul-2015::15:16:12 === Supervisor: {<0.1096.0>,
cowboy_requests_sup} Context: child_terminated Reason: {badarg, [{cowboy_
http,urldecode,3,[]}, {cowboy_dispatcher,'-do_split_path/3-lc$^0/1-0-',2,[]},
{cowboy_dispatcher,split_path,2,[]}, {cowboy_http_protocol,request,2,[]}]}
Offender: [{pid,<0.24019.228>}, {name,cowboy_requests_sup}, {mfargs,{cowboy_
requests_sup,start_request,undefined}}, {restart_type,temporary}, {shutdown,
brutal_kill}, {child_type,worker}]

[Michael Klishin]

Post by Tony
We occasionally see these in our RabbitMQ server v3.3.4 on Windows
SASL.log file. Are they significant? What do they indicate?
badarg...".

This means an Erlang process didn't terminate in an amount of time it was
given to do so and forcefully killed (and possibly then restarted). 

I'm not sure what mean lead to url decoding exceptions in Cowboy
(which is an HTTP and WebSocket server we use in rabbitmq-webstomp) but
our Cowboy version is outdated. We are starting the work on upgrading
it in the upcoming weeks.
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

[Tony]

Thanks for the quick response.

The errors were from v3.3.4, is Cowboy updated in v3.5.4?

Post by Michael Klishin

Post by Tony
We occasionally see these in our RabbitMQ server v3.3.4 on Windows
SASL.log file. Are they significant? What do they indicate?
badarg...".

This means an Erlang process didn't terminate in an amount of time it was
given to do so and forcefully killed (and possibly then restarted).
I'm not sure what mean lead to url decoding exceptions in Cowboy
(which is an HTTP and WebSocket server we use in rabbitmq-webstomp) but
our Cowboy version is outdated. We are starting the work on upgrading
it in the upcoming weeks.
--
MK
Staff Software Engineer, Pivotal/RabbitMQ

[Michael Klishin]

Post by Tony
The errors were from v3.3.4, is Cowboy updated in v3.5.4?

No,  3.5.4 uses the same Cowboy version.
--
MK

Staff Software Engineer, Pivotal/RabbitMQ