Hi Jay, I assume your NFS server monitored by Nagios too? If so can you monitor the disk/partition that /home on your servers point to on the NFS machine? i.e. have a /home check_disk service configured in Nagios to your NFS server host.
You could then set all 50 other machines' /home services to have a service dependency on the /home service on your NFS host. That way, if the service check on your 50 machines fails, Nagios will also check the /home service on your NFS host, and just send out the one notification. Regards, Andy Jay Chandler wrote: > I've got a scenario that I'd imagine many of you have already dealt > with, so before I roll my own solution I figured I'd ask y'all what > you've done. > > I have roughly 50 servers or so that mount their home directories (as > well as a few other things, but let's talk about /home for simplicity) > from an NFS server (isilon at the moment, shortly to become a NetApp). > > Because space is expensive, periodically central storage fills up. This > results in /home sending out notifications from all 50 servers. > > Is there a good way to set things up so that if central storage fills up > I don't get paged by every system we've got? I don't want to give up > monitoring /home on these hosts since our configuration monkey has > screwed up before and NOT mounted the NFS share, leading to the > mountpoint on local disk filling up instead. > > Thanks-- my apologies if this wasn't clear. > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
