Supervisor received unexpected message

457 views

Skip to first unread message

Johan Rhodin

unread,

Mar 31, 2019, 5:59:34 AM3/31/19

to rabbitm...@googlegroups.com

Hi,

(Erlang 20.1, RabbitMQ 3.6.14.)
I understand that the main recommendation is to upgrade RabbitMQ and Erlang to avoid this, but am curious to get an understanding of which supervisor received an unexpected messages in the following case. This looks somewhat similar to [1], which was fixed in [2].

/Johan

[1] https://groups.google.com/d/msg/rabbitmq-users/DUv1KGJVWTA/OLp4IvmkAwAJ
[2] https://github.com/rabbitmq/rabbitmq-server/issues/1699

---

Log file:

=ERROR REPORT==== 7-Feb-2019::14:26:38 ===
Supervisor received unexpected message: {'DOWN',
{delegate_11,<19880.23487.137>},
process,<19880.23487.137>,shutdown}

=ERROR REPORT==== 7-Feb-2019::14:26:40 ===
Supervisor received unexpected message: {'DOWN',
{delegate_11,<19880.4992.169>},
process,<19880.4992.169>,shutdown}

=ERROR REPORT==== 7-Feb-2019::14:26:42 ===
Supervisor received unexpected message: {'DOWN',
{delegate_8,<19880.25972.5906>},
process,<19880.25972.5906>,normal}

=ERROR REPORT==== 7-Feb-2019::14:26:42 ===
Supervisor received unexpected message: {'DOWN',
{delegate_1,<19880.25972.5906>},
process,<19880.25972.5906>,normal}

=ERROR REPORT==== 7-Feb-2019::14:26:42 ===
Supervisor received unexpected message: {'DOWN',
{delegate_11,<19880.25972.5906>},
process,<19880.25972.5906>,normal}

=ERROR REPORT==== 7-Feb-2019::14:26:42 ===
Supervisor received unexpected message: {'DOWN',
{delegate_3,<19880.25972.5906>},
process,<19880.25972.5906>,normal}

=ERROR REPORT==== 7-Feb-2019::14:26:42 ===
Supervisor received unexpected message: {'DOWN',
{delegate_8,<19880.25972.5906>},
process,<19880.25972.5906>,normal}

SASL log file:

=CRASH REPORT==== 7-Feb-2019::14:26:38 ===
crasher:
initial call: rabbit_reader:init/4
pid: <0.12866.4623>
registered_name: []
exception exit: {abnormal_dependent_exit,<19880.23487.137>,shutdown}
in function rabbit_reader:handle_dependent_exit/3
in call from rabbit_reader:mainloop/4
in call from rabbit_reader:run/1
in call from rabbit_reader:start_connection/4
ancestors: [<0.26946.6544>,<0.5615.0>,<0.5614.0>,<0.5613.0>,rabbit_sup,
<0.5254.0>]
message_queue_len: 1
messages: [{'EXIT',#Port<0.62128259>,normal}]
links: [<0.26946.6544>]
dictionary: [{{credit_from,<0.14933.7926>},397},
{process_name,
{rabbit_reader,
<<"aa.bbb.ccc.ddd:28698 -> 10.50.159.29:5672">>}},
{{ch_pid,<0.14933.7926>},
{1,#Ref<0.3573905785.1657798662.222355>}},
{credit_flow_default_credit,{400,200}},
{{channel,1},
{<0.14933.7926>,{method,rabbit_framing_amqp_0_9_1}}}]
trap_exit: true
status: running
heap_size: 610
stack_size: 27
reductions: 820424
neighbours:

=SUPERVISOR REPORT==== 7-Feb-2019::14:26:38 ===
Supervisor: {<0.26946.6544>,rabbit_connection_sup}
Context: child_terminated
Reason: {abnormal_dependent_exit,<19880.23487.137>,shutdown}
Offender: [{pid,<0.12866.4623>},
{name,reader},
{mfargs,
{rabbit_reader,start_link,
[<0.753.6588>,
{acceptor,{0,0,0,0},5672},
#Port<0.62128259>]}},
{restart_type,intrinsic},
{shutdown,30000},
{child_type,worker}]

=SUPERVISOR REPORT==== 7-Feb-2019::14:26:38 ===
Supervisor: {<0.26946.6544>,rabbit_connection_sup}
Context: shutdown
Reason: reached_max_restart_intensity
Offender: [{pid,<0.12866.4623>},
{name,reader},
{mfargs,
{rabbit_reader,start_link,
[<0.753.6588>,
{acceptor,{0,0,0,0},5672},
#Port<0.62128259>]}},
{restart_type,intrinsic},
{shutdown,30000},
{child_type,worker}]

Michael Klishin

unread,

Apr 23, 2019, 10:37:00 AM4/23/19

to rabbitmq-users

I don't think this is [1] as what terminated in this case was delegate processes. This is not a scenario I have seen before.

It can be that the supervisor structure was not set up correctly in that version. That's my best guess at least,

as something similar was discovered in earlier 3.x versions.

On Sun, Mar 31, 2019 at 12:59 PM Johan Rhodin <jo...@84codes.com> wrote:

Hi,

(Erlang 20.1, RabbitMQ 3.6.14.)
I understand that the main recommendation is to upgrade RabbitMQ and Erlang to avoid this, but am curious to get an understanding of which supervisor received an unexpected messages in the following case. This looks somewhat similar to [1], which was fixed in [2].

/Johan

[1] https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msg_rabbitmq-2Dusers_DUv1KGJVWTA_OLp4IvmkAwAJ&d=DwIFaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=wK8593osN75HgBaGPuOJ8rdBO5dnseij4hzid56kb34&m=t_pt8qG_45kxEc9IOtgrSmcJqpT1G6igwqoFFIAS_jo&s=9Wblkx-EHldzMzWG2wADrXe5doQP-capEYtHHLQ4xzw&e=

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send an email to rabbitm...@googlegroups.com.
For more options, visit https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=DwIFaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=wK8593osN75HgBaGPuOJ8rdBO5dnseij4hzid56kb34&m=t_pt8qG_45kxEc9IOtgrSmcJqpT1G6igwqoFFIAS_jo&s=nOCMJRgGpJ4pcqq_luaGKI6yszjmKnaFDED-ktdJMhw&e=.