<div dir="ltr"><div><div>Simon, thank you very much for your help!<br><br></div><div>Yes I figured that if my connection was closed those connections would not listed<br><br></div><div>I actually killed the connections yesterday and they kept coming back under different pids<br>
<br></div>I started the zenoss service that connects to rabbitmq and it looks like its trying to connect to a PID that does not exist which it sounds like from your e-mail that that is ok?<br><br></div>sorry I am running a little slow this morning but I couldn't get that command to work all together but was able to just run it with pid option<br>
<br>rabbitmqctl list_connections zenoss localhost client_properties pid<br>Listing connections ...<br>Error: {bad_argument,zenoss}<br><div><br>tail /var/log/rabbitmq/rabbit\@localhost.log<br>=ERROR REPORT==== 6-Sep-2013::08:56:25 ===<br>
closing AMQP connection <0.7417.0> (<a href="http://127.0.0.1:50621">127.0.0.1:50621</a> -> <a href="http://127.0.0.1:5672">127.0.0.1:5672</a>):<br>{bad_header,<<94,93,13,10,4,4,4,255>>}<br><br>=INFO REPORT==== 6-Sep-2013::09:01:00 ===<br>
accepting AMQP connection <0.7463.0> (<a href="http://127.0.0.1:50646">127.0.0.1:50646</a> -> <a href="http://127.0.0.1:5672">127.0.0.1:5672</a>)<br><br>=WARNING REPORT==== 6-Sep-2013::09:01:00 ===<br>closing AMQP connection <0.7463.0> (<a href="http://127.0.0.1:50646">127.0.0.1:50646</a> -> <a href="http://127.0.0.1:5672">127.0.0.1:5672</a>):<br>
connection_closed_abruptly<br><br>rabbitmqctl list_connections pid<br>Listing connections ...<br><rabbit@localhost.1.1042.0><br><rabbit@localhost.1.302.0><br><rabbit@localhost.1.1109.0><br><rabbit@localhost.1.352.0><br>
<rabbit@localhost.1.1126.0><br><rabbit@localhost.1.1062.0><br><rabbit@localhost.1.370.0><br><rabbit@localhost.1.306.0><br><rabbit@localhost.1.291.0><br>...done.<br><br></div><div>Is there anyway to turn on more logging? <br>
</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Sep 6, 2013 at 6:34 AM, 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">On 05/09/2013 9:09PM, Ken Henry wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
RabbitMQ runs fine on both hosts and host B gets an error when the<br>
Zenoss servers tries to connect to rabbitmq<br>
<br>
=INFO REPORT==== 5-Sep-2013::15:11:36 ===<br>
accepting AMQP connection <0.470.0> (<a href="http://127.0.0.1:44024" target="_blank">127.0.0.1:44024</a> -> <a href="http://127.0.0.1:5672" target="_blank">127.0.0.1:5672</a>)<div class="im"><br>
<br>
=WARNING REPORT==== 5-Sep-2013::15:11:36 ===<br>
closing AMQP connection <0.470.0> (<a href="http://127.0.0.1:44024" target="_blank">127.0.0.1:44024</a> -> <a href="http://127.0.0.1:5672" target="_blank">127.0.0.1:5672</a>):<br>
connection_closed_abruptly<br>
</div></blockquote>
<br>
That's to be expected if the connection is not actually talking AMQP. You can suppress these warnings, see 'log_levels' at <a href="http://www.rabbitmq.com/configure.html" target="_blank">http://www.rabbitmq.com/<u></u>configure.html</a><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
rabbitmqctl list_connections<br>
Listing connections ...<br>
zenoss 127.0.0.1 43982 running<br>
zenoss 127.0.0.1 43981 running<br>
zenoss 127.0.0.1 43979 running<br>
zenoss 127.0.0.1 43989 running<br>
zenoss 127.0.0.1 43994 running<br>
zenoss 127.0.0.1 43980 running<br>
zenoss 127.0.0.1 43969 running<br>
zenoss 127.0.0.1 43988 running<br>
zenoss 127.0.0.1 43985 running<br>
...done.<br>
<br>
I am guessing these connections were made originally before the<br>
connection was closed abruptly?<br>
</blockquote>
<br>
So I assume the problem is that you don't think these connections should be listed, since you think they were short-lived not-really-AMQP connections from a monitoring tool?<br>
<br>
Connections which have been closed (abruptly or not) should really not make it to this list. You might want to attempt to correlate the connection pid (e.g. "<0.470.0>" from the log above) with the results of "rabbitmqctl list_connections user peer_host peer_port pid state". If you see the same pid in both, that's a bug.<br>
<br>
But actually I think those are real client connections that have somehow been routed to your host B, since the ones from zenoss should never have got as far as the 'running' state.<br>
<br>
"rabbitmqctl list_connections user peer_host peer_port client_properties" might be illuminating - this will add a column listing the self-declared client properties to the output, only real AMQP clients will have such properties.<br>
<br>
Cheers, Simon<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, Pivotal<br>
</font></span></blockquote></div><br></div>