I suppose it depends on the level of certainty one is looking for. Checking that the port is open doesn't mean that rabbit is capable of receiving/sending messages (eg: SSL listener bug, etc...). I guess the only real way to monitor would� be to connect, publish, and consume.<br>
<br><br><br><div class="gmail_quote">On Thu, Jan 28, 2010 at 7:00 AM, Matthew Sackman <span dir="ltr"><<a href="mailto:matthew@lshift.net" target="_blank">matthew@lshift.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Mark,<br>
<br>
On Tue, Jan 26, 2010 at 03:42:39PM -0500, Mark Steele wrote:<br>
> I'm trying to find a good way to monitor rabbit for inclusion in an HA<br>
> cluster (pacemaker/corosync).<br>
><br>
> Does anyone have a good resource agent already created for such a purpose?<br>
<br>
We don't have one off the shelf, though several of our clients are using<br>
RabbitMQ with pacemaker and heartbeat, and presumeably have written similar<br>
such scripts.<br>
<br>
Rather than using the rabbitmq-multi script to monitor (which should be<br>
fine), we tend to suggest just checking to see if the port is open (by<br>
default 5672, but that can change on configuration). How does pacemaker<br>
monitor something like apache? - again there would be the option of<br>
either checking the port is open, or using some sort of status<br>
monitoring. I don't know whether one is generally preferred to the<br>
other?<br>
<br>
Matthew<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Mark Steele<br>Director of development<br>Bering Media Inc.<br><br>