<div dir="ltr">ok, I got keepalived above the cluster. And is balancing 61613 and 5672<div>could be keepalived opening and not closing something properly?</div><div>I undertstand the connections are being close well, but ..</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Sep 26, 2013 at 4:18 PM, Santi Nu�ez-Cacho <span dir="ltr"><<a href="mailto:brian.santiago@gmail.com" target="_blank">brian.santiago@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">yes, I do<div><br></div><div><div>=INFO REPORT==== 26-Sep-2013::16:12:46 ===</div><div>accepting STOMP connection <0.19254.0> (XX:49217 -> YY:61613)</div>
</div><div><br></div><div><div>=INFO REPORT==== 26-Sep-2013::16:12:46 ===</div>
<div>closing STOMP connection <0.19254.0> (XX:49217 -> YY:61613)</div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Sep 26, 2013 at 4:07 PM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hmm. Something must be establishing short-lived stomp connections though, do you see lines like:<br>
<br>
� =INFO REPORT==== 26-Sep-2013::15:06:39 ===<br>
� accepting STOMP connection <0.376.0> ([::1]:56780 -> [::1]:61613)<br>
<br>
in the log?<br>
<br>
Cheers, Simon<div><br>
<br>
On 26/09/2013 2:07PM, Santi Nu�ez-Cacho wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
It was the connetion to the mcollective rabbitmq middleware. ( we 've<br>
got all the machines connected to mcollective )<br>
<br>
I removed the mcollective conection. Disabling it. And restarting the<br>
rabbitmq-server.<br>
<br>
That's we got now<br>
<br>
<br>
[root@rabbit03.bcn rabbitmq]# lsof -i :61613<br>
COMMAND � �PID � � USER � FD � TYPE �DEVICE SIZE/OFF NODE NAME<br>
beam.smp 17472 rabbitmq � 21u �IPv6 4652854 � � �0t0 �TCP *:61613 (LISTEN)<br>
[root@rabbit03.bcn rabbitmq]# �rabbitmqctl eval<br>
'length(supervisor:which_<u></u>children(rabbit_stomp_client_<u></u>sup_sup)).'<br>
50<br>
...done.<br>
[root@rabbit03.bcn rabbitmq]#<br>
<br>
And the process growing...<br>
<br>
<br>
<br>
<br>
On Thu, Sep 26, 2013 at 2:57 PM, Simon MacMullen <<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a><br></div><div>
<mailto:<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>>> wrote:<br>
<br>
� � On 26/09/2013 1:51PM, Santi Nu�ez-Cacho wrote:<br>
<br>
� � � � I expect 0 stomp connetions. The unique one connection on 61613<br>
� � � � should<br>
� � � � be the cluster one.<br>
<br>
<br>
� � Port 61613 is not used for clustering, it's just stomp.<br>
<br>
<br>
� � � � [root@rabbit03.bcn ~]# �rabbitmqctl eval<br></div>
� � � � 'length(supervisor:which___<u></u>children(rabbit_stomp_client__<u></u>_sup_sup)).'<div><br>
� � � � 3802<br>
� � � � ...done.<br>
� � � � [root@rabbit03.bcn ~]# lsof -i :61613<br>
� � � � COMMAND � �PID � � USER � FD � TYPE �DEVICE SIZE/OFF NODE NAME<br>
� � � � ruby � � �5638 � � root � �6u �IPv4 � 25097 � � �0t0 �TCP<br></div>
� � � � rabbit03.bcn.softonic.lan:__<u></u>59851->rabbit:61613 (ESTABLISHED)<div><br>
� � � � beam.smp 27183 rabbitmq � 21u �IPv6 4521334 � � �0t0 �TCP<br>
� � � � *:61613 (LISTEN)<br>
<br>
<br>
� � Ah.<br>
<br>
� � So you have one connection, from some ruby script. But 3802<br>
� � connection processes. So something is somehow leaking. Thank you for<br>
� � reporting this bug.<br>
<br>
� � But to help get to the bottom of it - what is that ruby script doing?<br>
<br>
<br>
� � Cheers, Simon<br>
<br>
� � --<br>
� � Simon MacMullen<br>
� � RabbitMQ, Pivotal<br>
<br>
<br>
</div></blockquote><div><div>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, Pivotal<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>