[rabbitmq-discuss] Rabbitmq up and running but connection_closed_abruptly

[Simon MacMullen]

On 05/09/2013 9:09PM, Ken Henry wrote:
> RabbitMQ runs fine on both hosts and host B gets an error when the
> Zenoss servers tries to connect to rabbitmq
>
> =INFO REPORT==== 5-Sep-2013::15:11:36 ===
> accepting AMQP connection <0.470.0> (127.0.0.1:44024 -> 127.0.0.1:5672)
>
> =WARNING REPORT==== 5-Sep-2013::15:11:36 ===
> closing AMQP connection <0.470.0> (127.0.0.1:44024 -> 127.0.0.1:5672):
> connection_closed_abruptly

That's to be expected if the connection is not actually talking AMQP. 
You can suppress these warnings, see 'log_levels' at 
http://www.rabbitmq.com/configure.html

> rabbitmqctl list_connections
> Listing connections ...
> zenoss  127.0.0.1       43982   running
> zenoss  127.0.0.1       43981   running
> zenoss  127.0.0.1       43979   running
> zenoss  127.0.0.1       43989   running
> zenoss  127.0.0.1       43994   running
> zenoss  127.0.0.1       43980   running
> zenoss  127.0.0.1       43969   running
> zenoss  127.0.0.1       43988   running
> zenoss  127.0.0.1       43985   running
> ...done.
>
> I am guessing these connections were made originally before the
> connection was closed abruptly?

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?

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.

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.

"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.

Cheers, Simon

-- 
Simon MacMullen
RabbitMQ, Pivotal