On Fri, Apr 1, 2011 at 10:56 AM, Lars Ellenberg <[email protected]> wrote: > But possibly you should rather have some monitoring (nagios, ...) notice this, > page/email/alert with your favorite method the relevant people, and have > them take appropriate actions? >
Ok, lets see how this might work. You would need a separate monitor for the cluster and since this monitor also can potentially crash, you would need another monitor to observer the first one, then we would want the first one to monitor second one, so we would need a cluster of monitors. Wait, don't we have already cluster in place? It seems logical to have monitor to be part of the cluster. I was expecting "monitor" operation to handle that, but it seems for DRBD this is not the case. Maybe we should have another primitive running? drbd_status or something? When drbd subsystem is in degraded state, have drbd_status in "stopped" state? Vadym _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
