[rabbitmq-discuss] Rabbitmq up and running but connection_closed_abruptly

[Ken Henry]

Hi Simon,

Thanks for your help. It is working now! I am not exactly sure what made it
work. A restart was one thing


On Fri, Sep 6, 2013 at 1:20 PM, Ken Henry <kenhen93 at gmail.com> wrote:

> Hi Simon,
>
> I am not trying to monitor rabbitmq. Rabbitmq is part of the new version
> of Zenoss.
>
> I setup my new Zenoss installation in a Veritas cluster that has a SAN and
> VIP that fail back and forth between the hosts.
>
> Zenoss and RabbitMQ work fine on Node A but not on Node B. I don't see any
> difference in the setup from Node A to Node B.
>
> If this were working right, I could failover to Node B and RabbitMQ would
> allow Zenhub (a zenoss service) to connect to it. Zenhub logs tell me
> RabbitMQ is refusing its connection.
>
> Thank you for any help!
>
> Cheers
>
>
> On Fri, Sep 6, 2013 at 11:49 AM, Simon MacMullen <simon at rabbitmq.com>wrote:
>
>> On 06/09/2013 3:51PM, Ken Henry wrote:
>>
>>> Simon,
>>>
>>> Anything else you can think of to troubleshoot more?
>>>
>>
>>  You are essential saying that Zenoss is at fault?
>>>
>>
>> I still don't think I am 100% sure what you are saying your problem is.
>> Are you saying:
>>
>> 1) Zenoss should be connecting to node A and node B to monitor them
>> 2) It should also be routing connections from clients to node A but not
>> node B since node A has not failed
>> 3) But you're seeing long-lived connections to node B, which shouldn't be
>> happening
>>
>> That's what I've understood from you.
>>
>> However, I've just Googled "zenoss rabbitmq" and they claim their plugin
>> monitors RabbitMQ by invoking rabbitmqctl over ssh. So I don't think that
>> adds up with what I've understood.
>>
>> So please can you explain what you expect to be happening, and why the
>> results you're seeing don't match your expectations?
>>
>> Cheers, Simon
>>
>>
>>>
>>> On Fri, Sep 6, 2013 at 9:30 AM, Simon MacMullen <simon at rabbitmq.com
>>> <mailto:simon at rabbitmq.com>> wrote:
>>>
>>>     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<http://www.rabbitmq.com/man/__rabbitmqctl.1.man.html#list___connections>
>>>
>>>     <http://www.rabbitmq.com/man/**rabbitmqctl.1.man.html#list_**
>>> connections<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
>>>
>>>
>>>
>> --
>> Simon MacMullen
>> RabbitMQ, Pivotal
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130906/e84ebafd/attachment.htm>