<div dir="ltr">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:<div><br></div><div><div>=ERROR REPORT==== 15-Aug-2013::11:02:42 ===</div>
<div>** Generic server delegate_0 terminating</div><div>** Last message in was {'DOWN',#Ref<0.0.2498.72665>,process,<2986.16099.3104>,</div><div>� � � � � � � � � � � � � � � �normal}</div><div>** When Server state == {state,'rabbit@428178-data15',</div>
<div>� � � � � � � � � � � � � � � �{dict,2,16,16,8,80,48,</div><div>� � � � � � � � � � � � � � � � � � �{[],[],[],[],[],[],[],[],[],[],[],[],[],</div><div>� � � � � � � � � � � � � � � � � � � [],[],[]},</div><div>� � � � � � � � � � � � � � � � � � �{{[],</div>
<div>� � � � � � � � � � � � � � � � � � � �[[<2986.16099.3104>|</div><div>� � � � � � � � � � � � � � � � � � � � �{<0.18153.2029>,</div><div>� � � � � � � � � � � � � � � � � � � � � #Ref<0.0.2498.72669>}]],</div>
<div>� � � � � � � � � � � � � � � � � � � �[[<2986.15096.3096>|</div><div>� � � � � � � � � � � � � � � � � � � � �{<0.18155.2029>,</div><div>� � � � � � � � � � � � � � � � � � � � � #Ref<0.0.2497.259319>}]],</div>
<div>� � � � � � � � � � � � � � � � � � � �[],[],[],[],[],[],[],[],[],[],[],[],</div><div>� � � � � � � � � � � � � � � � � � � �[]}}},</div><div>� � � � � � � � � � � � � � � �delegate_0}</div><div>** Reason for termination ==�</div>
<div>** {{case_clause,{ok,{<0.18153.2029>,#Ref<0.0.2498.72669>}}},</div><div>� � [{delegate,handle_info,2,[]},</div><div>� � �{gen_server2,handle_msg,2,[]},</div><div>� � �{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,239}]}]}</div>
</div><div><br></div><div>I've also just noticed now that we have publisher connections that are stuck too. In the connections view�</div></div><div class="gmail_extra"><br clear="all"><div>Paul Bowsher</div>
<br><br><div class="gmail_quote">On Thu, Aug 15, 2013 at 10:54 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Paul,<div class="im"><br>
<br>
On 15/08/13 10:50, Paul Bowsher wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for the reply. When you say resource alarms, do you mean on the<br>
server or from the clients?<br>
</blockquote>
<br></div>
Server.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It seems that we have a sick rabbit on node A. How can we<br>
help diagnose this?<br>
</blockquote>
<br></div>
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.<span class="HOEnZb"><font color="#888888"><br>
<br>
Matthias.<br>
</font></span></blockquote></div><br></div>