sorry, i hit reply instead of reply all
---------- Forwarded message ---------- From: alexus <[EMAIL PROTECTED]> Date: Nov 15, 2007 3:55 PM Subject: Re: [Nagios-users] check_disk To: "Valdinger, Stephen (DOV, MSX)" <[EMAIL PROTECTED]> well, defining service as you defined for me, i have no problem doing that, but i was hoping maybe there is something else besides check_disk that can see if external storage is exists/attached to my box, and i really didnt want to hardcode devices and/or mount points as if something adds changes it wouldnt pick it up on the fly, while if you not using -p in check_disk plugin it would have pick up anything that is available, in my case its also a bad thing since if drive isn't available then check_disk wouldn't even see that either, it can only say if there is an issue with disk space and that is it. On Nov 15, 2007 3:39 PM, Valdinger, Stephen (DOV, MSX) <[EMAIL PROTECTED]> wrote: > > > -----Original Message----- > From: alexus [mailto:[EMAIL PROTECTED] > > Sent: Thursday, November 15, 2007 3:32 PM > To: Valdinger, Stephen (DOV, MSX) > Subject: Re: [Nagios-users] check_disk > > local (nagios) > nagios 2.9 > check_disk (nagios-plugins 1.4.5) 1.79 > Red Hat Enterprise Linux ES release 4 (Nahant Update 5) > > remote (ext) > check_disk (nagios-plugins 1.4.2) 1.57 > Red Hat Enterprise Linux ES release 3 (Taroon Update 9) > > fdisk -l (without) external enclosure attached: > [EMAIL PROTECTED] root]# fdisk -l > > Disk /dev/cciss/c0d0: 146.8 GB, 146807930880 bytes > 255 heads, 32 sectors/track, 35139 cylinders > Units = cylinders of 8160 * 512 = 4177920 bytes > > Device Boot Start End Blocks Id System > /dev/cciss/c0d0p1 * 1 25 101984 83 Linux > /dev/cciss/c0d0p2 26 34638 141221040 83 Linux > /dev/cciss/c0d0p3 34639 35139 2044080 82 Linux swap > [EMAIL PROTECTED] root]# > > > and this is with external enclosure attached: > > [EMAIL PROTECTED] root]# fdisk -l > > Disk /dev/cciss/c1d0: 291.3 GB, 291334717440 bytes > 255 heads, 32 sectors/track, 69732 cylinders > Units = cylinders of 8160 * 512 = 4177920 bytes > > Disk /dev/cciss/c1d0 doesn't contain a valid partition table > > Disk /dev/cciss/c1d1: 587.2 GB, 587243773952 bytes > 255 heads, 63 sectors/track, 71394 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > > Disk /dev/cciss/c1d1 doesn't contain a valid partition table > > Disk /dev/cciss/c0d0: 146.8 GB, 146807930880 bytes > 255 heads, 32 sectors/track, 35139 cylinders > Units = cylinders of 8160 * 512 = 4177920 bytes > > Device Boot Start End Blocks Id System > /dev/cciss/c0d0p1 * 1 25 101984 83 Linux > /dev/cciss/c0d0p2 26 34638 141221040 83 Linux > /dev/cciss/c0d0p3 34639 35139 2044080 82 Linux swap > [EMAIL PROTECTED] root]# > ##################################################### > > > > Disk /dev/cciss/c1d1: 587.2 GB, 587243773952 bytes > 255 heads, 63 sectors/track, 71394 cylinders Units = cylinders of 16065 * 512 > = 8225280 bytes > > Disk /dev/cciss/c1d1 doesn't contain a valid partition table > > I'm going to wager a guess that this is the external scsi drive. > > As such, here is a basic command definition for check_disk > > define service{ > host_name linuxhost > command_name check_disk!/dev/cciss/c1d1!75!90 > service_description External SCSI Disk > } > > This is just a very basic service definition that supplies the location of > the disk to $ARG1$, warning criteria to $ARG2$, and critical criteria to > $ARG3$. This is not all conclusive, as I have no idea what you have defined > in your service template. > > Stephen Valdinger > > > > -- http://alexus.org/ -- http://alexus.org/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
