[rabbitmq-discuss] Orphaned channels after connection close in Rabbit 3.1.4

[Paul Bowsher]

Oops sorry, premature send. In the connections view they don't say blocked,
flow or running. When you click the connection it doesn't have a "state" at
all. However rabbitmqctl list_connections lists them as blocked.

These publishers are still publishing to node A, and again there's no stuck
connections on node B. Both nodes are identical hardware (not VMs), and are
completely fine in terms of resource.

Paul Bowsher


On Thu, Aug 15, 2013 at 11:11 AM, Paul Bowsher <paul.bowsher at gmail.com>wrote:

> Nope, nothing at all. When we have seen this issue "live" all the resource
> indicators on the Overview page are green by a long way. The only error we
> have in the logs is:
>
> =ERROR REPORT==== 15-Aug-2013::11:02:42 ===
> ** Generic server delegate_0 terminating
> ** Last message in was
> {'DOWN',#Ref<0.0.2498.72665>,process,<2986.16099.3104>,
>                                normal}
> ** When Server state == {state,'rabbit at 428178-data15',
>                                {dict,2,16,16,8,80,48,
>
>  {[],[],[],[],[],[],[],[],[],[],[],[],[],
>                                       [],[],[]},
>                                      {{[],
>                                        [[<2986.16099.3104>|
>                                          {<0.18153.2029>,
>                                           #Ref<0.0.2498.72669>}]],
>                                        [[<2986.15096.3096>|
>                                          {<0.18155.2029>,
>                                           #Ref<0.0.2497.259319>}]],
>                                        [],[],[],[],[],[],[],[],[],[],[],[],
>                                        []}}},
>                                delegate_0}
> ** Reason for termination ==
> ** {{case_clause,{ok,{<0.18153.2029>,#Ref<0.0.2498.72669>}}},
>     [{delegate,handle_info,2,[]},
>      {gen_server2,handle_msg,2,[]},
>      {proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,239}]}]}
>
> I've also just noticed now that we have publisher connections that are
> stuck too. In the connections view
>
> Paul Bowsher
>
>
> On Thu, Aug 15, 2013 at 10:54 AM, Matthias Radestock <
> matthias at rabbitmq.com> wrote:
>
>> Paul,
>>
>>
>> On 15/08/13 10:50, Paul Bowsher wrote:
>>
>>> Thanks for the reply. When you say resource alarms, do you mean on the
>>> server or from the clients?
>>>
>>
>> Server.
>>
>>
>>  It seems that we have a sick rabbit on node A. How can we
>>> help diagnose this?
>>>
>>
>> Check the logs and the management UI. For connections to be in the
>> 'blocked' state for any significant duration of time, there must be a
>> triggering memory and/or disk alarm. Which should be very obvious in the
>> logs and UI.
>>
>> Matthias.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130815/339dfbe9/attachment.htm>