On Fri, Nov 13, 2009 at 2:44 PM, Terry td3...@gmail.com wrote:
Hello,
I have an nsclient++ checkdrivesize check in place. There is a weird
condition where with microsoft clusters, after a failover event, the
passive node still has the drive letters around. This causes the
check to return
So the issue is that you have a single check that checks all the drives on
the machine, and then return whatever it considers the worst state - in
this case UNKNOWN?
Couldn't you simply have one check per drive? This way, you'll know if more
than one drive goes out of disk space at the same time
This is what I ended up doing. Here's a snippet of checking both
cluster nodes and the cluster drives themselves. Sorry for not
thinking outside of the box to begin with:
define service {
use service-active-perf-30
host_name cluster1a,cluster1b
Hello,
I have an nsclient++ checkdrivesize check in place. There is a weird
condition where with microsoft clusters, after a failover event, the
passive node still has the drive letters around. This causes the
check to return an unknown status for those drives:
: UNKNOWN: Could not get
