Bug 1466803 - rabbitmqctl list_queues will hang
Summary: rabbitmqctl list_queues will hang
Keywords:
Status: CLOSED DUPLICATE of bug 1434593
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rabbitmq-server
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Peter Lemenkov
QA Contact: Udi Shkalim
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-30 13:41 UTC by bigswitch
Modified: 2017-06-30 13:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-30 13:56:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description bigswitch 2017-06-30 13:41:09 UTC
Description of problem:
While debugging slow performance in RHOSP 10 setup with three controllers, notice rabbitmqctl list_queues will hang at the bottom and entering CTRL-C to exit. Not sure if this is an issue, filing bz for tracking.

[root@overcloud-controller-1 neutron]# rabbitmqctl list_queues
Listing queues ...
q-reports-plugin_fanout_eb4200d083b14100895ae49c626d341e        0
engine_worker_fanout_9a4e1c6ca9d848f6ad2e95bea3ae5324   0
heat-engine-listener.bf68bf7d-9ebe-4f79-8557-8213720c9d69       0
engine_worker.ba5d613e-d434-4579-a7e7-876ec4bbc0a1      0
q-server-resource-versions_fanout_abc26d61b767482cbbef382db0f5e94b      0
heat-engine-listener_fanout_6ded4ef2a85d40008396c2af299424e3    0
q-server-resource-versions_fanout_c7d3568b2cd64953817c8ce5aa68438b      0
q-reports-plugin_fanout_c98f9ff0308945ddae85a780821f2e82        0
q-server-resource-versions_fanout_23b2519c5de045c9ad7904d75fcbe82b      0
q-reports-plugin_fanout_0db4f5c022ff4f1e8b94a9decd63688f        0
...

^C
Session terminated, killing shell...


 ...killed.
[root@overcloud-controller-1 neutron]#

Googling around I found this:

[root@overcloud-controller-1 heat-admin]# rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().'
2017-06-29 14:11:25 There are 6088 processes.
2017-06-29 14:11:25 Investigated 1 processes this round, 5000ms to go.
2017-06-29 14:11:25 Investigated 1 processes this round, 4500ms to go.
2017-06-29 14:11:26 Investigated 1 processes this round, 4000ms to go.
2017-06-29 14:11:26 Investigated 1 processes this round, 3500ms to go.
2017-06-29 14:11:27 Investigated 1 processes this round, 3000ms to go.
2017-06-29 14:11:27 Investigated 1 processes this round, 2500ms to go.
2017-06-29 14:11:28 Investigated 1 processes this round, 2000ms to go.
2017-06-29 14:11:28 Investigated 1 processes this round, 1500ms to go.
2017-06-29 14:11:29 Investigated 1 processes this round, 1000ms to go.
2017-06-29 14:11:29 Investigated 1 processes this round, 500ms to go.
2017-06-29 14:11:30 Found 1 suspicious processes.
2017-06-29 14:11:30 [{pid,<10374.31617.1>},
                     {registered_name,[]},
                     {current_stacktrace,
                         [{rabbit_control_misc,collect_monitors,1,
                              [{file,"src/rabbit_control_misc.erl"},
                               {line,124}]},
                          {rpc,'-handle_call_call/6-fun-0-',5,
                              [{file,"rpc.erl"},{line,206}]}]},
                     {initial_call,{erlang,apply,2}},
                     {message_queue_len,1},
                     {links,[<10545.15886.3>,<10546.21055.3>]},
                     {monitors,
                         [{process,<10545.15886.3>},
                          {process,<10546.21055.3>}]},
                     {monitored_by,[<10374.14.0>]},
                     {heap_size,233}]
ok


Version-Release number of selected component (if applicable):
RHOSP10

How reproducible:
Always

Comment 1 Peter Lemenkov 2017-06-30 13:56:43 UTC
Yes, it's an issue. Fortunately a known one (refer to bug 1434593 for further details).

Please check if the issue is reproducible with rabbitmq-server-3.6.3-7.el7ost. If it's still there, then reopen this ticket.

*** This bug has been marked as a duplicate of bug 1434593 ***


Note You need to log in before you can comment on or make changes to this bug.