2008/9/29 Jay Chandler <[EMAIL PROTECTED]>: > 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. > > -- > Jay Chandler / KB1JWQ > Living Legend / Systems Exorcist > Today's Excuse: bit bucket overflow >
Can you check the FS directly on the NFS server?, that would be better, and just check that the FS is mounted on your 50 clients... To check mount points: http://www.nagiosexchange.org/cgi-bin/page.cgi?g=2588.html;d=1 http://www.nagiosexchange.org/cgi-bin/page.cgi?g=1334.html;d=1 http://www.nagiosexchange.org/cgi-bin/page.cgi?g=1552.html;d=1 http://www.nagiosexchange.org/cgi-bin/page.cgi?g=2172.html;d=1 Regards, Ciro ------------------------------------------------------------------------- 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