[rabbitmq-discuss] Rabbitmq up and running but connection_closed_abruptly

[Simon MacMullen]

On 06/09/2013 2:23PM, Ken Henry wrote:
> Simon, thank you very much for your help!
>
> Yes I figured that if my connection was closed those connections would
> not listed
>
> I actually killed the connections yesterday and they kept coming back
> under different pids
>
> 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?

The pid is effectively just a connection identifier in this case. So if 
the connections logging as "closed_abruptly" don't show up under 
"rabbitmqctl list_connections" I'd say you're good.

> 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
>
> rabbitmqctl list_connections zenoss localhost client_properties pid
> Listing connections ...
> Error: {bad_argument,zenoss}

You don't need to make substitutions there - I mean literally 
"rabbitmqctl list_connections user peer_host peer_port client_properties 
pid". That command means "give me a listing with columns for user, peer 
host, etc". See 
http://www.rabbitmq.com/man/rabbitmqctl.1.man.html#list_connections for 
more details.

> Is there anyway to turn on more logging?

Afraid not.

Cheers, Simon


-- 
Simon MacMullen
RabbitMQ, Pivotal