<div dir="ltr">Hi Simon,<br><br>Thanks for your help. It is working now! I am not exactly sure what made it work. A restart was one thing<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Sep 6, 2013 at 1:20 PM, Ken Henry <span dir="ltr"><<a href="mailto:kenhen93@gmail.com" target="_blank">kenhen93@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"><div><div><div><div><div><div>Hi Simon,<br><br></div>I am not trying to monitor rabbitmq. Rabbitmq is part of the new version of Zenoss.<br>
<br></div>I setup my new Zenoss installation in a Veritas cluster that has a SAN and VIP that fail back and forth between the hosts.<br>
<br></div>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.<br><br></div>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.<br>
<br></div>Thank you for any help!<br><br></div>Cheers<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Sep 6, 2013 at 11:49 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"><div>On 06/09/2013 3:51PM, Ken Henry wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Simon,<br>
<br>
Anything else you can think of to troubleshoot more?<br>
</blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You are essential saying that Zenoss is at fault?<br>
</blockquote>
<br></div>
I still don't think I am 100% sure what you are saying your problem is. Are you saying:<br>
<br>
1) Zenoss should be connecting to node A and node B to monitor them<br>
2) It should also be routing connections from clients to node A but not node B since node A has not failed<br>
3) But you're seeing long-lived connections to node B, which shouldn't be happening<br>
<br>
That's what I've understood from you.<br>
<br>
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.<br>
<br>
So please can you explain what you expect to be happening, and why the results you're seeing don't match your expectations?<br>
<br>
Cheers, Simon<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<br>
<br>
On Fri, Sep 6, 2013 at 9:30 AM, Simon MacMullen <<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a><br></div><div><div>
<mailto:<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>>> wrote:<br>
<br>
� � On 06/09/2013 2:23PM, Ken Henry wrote:<br>
<br>
� � � � Simon, thank you very much for your help!<br>
<br>
� � � � Yes I figured that if my connection was closed those connections<br>
� � � � would<br>
� � � � not listed<br>
<br>
� � � � I actually killed the connections yesterday and they kept coming<br>
� � � � back<br>
� � � � under different pids<br>
<br>
� � � � I started the zenoss service that connects to rabbitmq and it<br>
� � � � looks like<br>
� � � � its trying to connect to a PID that does not exist which it<br>
� � � � sounds like<br>
� � � � from your e-mail that that is ok?<br>
<br>
<br>
� � The pid is effectively just a connection identifier in this case. So<br>
� � if the connections logging as "closed_abruptly" don't show up under<br>
� � "rabbitmqctl list_connections" I'd say you're good.<br>
<br>
<br>
� � � � sorry I am running a little slow this morning but I couldn't get<br>
� � � � that<br>
� � � � command to work all together but was able to just run it with<br>
� � � � pid option<br>
<br>
� � � � rabbitmqctl list_connections zenoss localhost client_properties pid<br>
� � � � Listing connections ...<br>
� � � � Error: {bad_argument,zenoss}<br>
<br>
<br>
� � You don't need to make substitutions there - I mean literally<br>
� � "rabbitmqctl list_connections user peer_host peer_port<br>
� � client_properties pid". That command means "give me a listing with<br>
� � columns for user, peer host, etc". See<br></div></div>
� � <a href="http://www.rabbitmq.com/man/__rabbitmqctl.1.man.html#list___connections" target="_blank">http://www.rabbitmq.com/man/__<u></u>rabbitmqctl.1.man.html#list___<u></u>connections</a><div><br>
� � <<a href="http://www.rabbitmq.com/man/rabbitmqctl.1.man.html#list_connections" target="_blank">http://www.rabbitmq.com/man/<u></u>rabbitmqctl.1.man.html#list_<u></u>connections</a>> for<br>
� � more details.<br>
<br>
<br>
� � � � Is there anyway to turn on more logging?<br>
<br>
<br>
� � Afraid not.<br>
<br>
<br>
� � Cheers, Simon<br>
<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>