[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] Monitoring Failovers

It is a little bit hard to do. It is on my todo list too. The problem is
to determine the old state. So for example if you switch an ip address
and you have a service bound to that address you have nearly no chance
to monitor it from the Nagios side. 

I have tested using the MAC address and arp but this is awesome if you
have bonding. Because if the MAC switches it may be the bonding of the
cluster or the cluster switched. But hardcoded MAC addresses in the
monitor script will not be good idea.

Too much trouble in maintenance.

If anyone has a good idea I will write the plugin and post it

Martin Fuerstenau

On Fri, 2009-02-20 at 11:04 -0500, Burton Simonds wrote:
> I am in the process of setting up Nagios for system monitoring, and I
> would like to have a way to know if a failover has occurred.  If
> everything works as it should, there be a minimal impact on the
> services.  Right now it looks like my best bet is basically scrape the
> logs and look for the failover messages there and trigger an alarm.
> I was wondering if anyone else has done anything.  I found in an
> archive a check_rhcs script that I am going to employ (which looks
> pretty cool), but that just looks at the status of the services.  I
> want to either compare the current status to the previous status or
> have something monitoring the cluster an pushes the alert to Nagios.
> Thanks,
> B
> --
> Linux-cluster mailing list
> Linux-cluster redhat com
> https://www.redhat.com/mailman/listinfo/linux-cluster

This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.

If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.

If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message.

Thank you for your co-operation.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]