check_nt syntax for USEDDISKSPACE in checkcommand.cfg

[Jo Knight]

Thanks, I got it working with your advice.

----- Original Message -----
From: "Tony" <nagios at cerbernet.co.uk>
To: <joknight at blueyonder.co.uk>; <Nagios-users at lists.sourceforge.net>
Sent: Thursday, February 13, 2003 1:49 PM
Subject: RE: [Nagios-users] check_nt syntax for USEDDISKSPACE in
checkcommand.cfg


> I would guess because you have not supplied any "warning" or "critical"
> values for nagios to act upon.
> If it does not see any CRITICAL, OK or WARNING values then I am not
> surprised it has not produced any output.
>
> To your checkcommand entry you would be better putting
>
> $USER1$/check_nt -H $HOSTADDRESS -v USEDDISKSPACE -l d $ARG1$ -w $ARG2$
> -c $ARG3$
>
> $ARG1$ = Partition
> $ARG2$ = Warning value in % used
> $ARG3$ = Warning value in % used
>
>
> And your service.cfg entry would be something like
>
>
> define service{
>         use                             generic-nt-server
>         host_name                       nt_server
>         service_description             D DISK
>         is_volatile                     0
>         contact_groups                  nt_contacts
>         check_command                   check_nt_disk!D!80!90
>         }
>
> Here is specified $ARG1$, $ARG2$ and $ARG3$ each separated by a "!".
>
> Obviously change the host_name, contact_groups and the service template
> to use.
> By doing it this way you can use the same checkcommand definition for
> all partitions on you NT boxes.
>
> Hope this helps.
>
> Tony
>
> > -----Original Message-----
> > From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> > admin at lists.sourceforge.net] On Behalf Of joknight at blueyonder.co.uk
> > Sent: 13 February 2003 12:56
> > To: Nagios-users at lists.sourceforge.net
> > Subject: [Nagios-users] check_nt syntax for USEDDISKSPACE in
> > checkcommand.cfg
> >
> > Hi,
> >
> > I have just set Nagios up and am trying to get the check_nt command
> configured
> > correctly to monitor diskspace. I have installed the nsclient service
> on a few
> > NT/2000 servers and have copied the check_nt binary into the libexec
> directory. I
> > can run the check_nt command with the -v USEDDISKSPACE -l
> <drive-letter>
> > manually and it reports the free space on the drive with no problems.
> >
> > When I looked in my checkcommand.cfg there was no entry for check_nt,
> so I
> > added the following:
> >
> > define command{
> >         command_name    check_nt_space_d
> >         command_line    $USER1$/check_nt -H $HOSTADDRESS -v
> > USEDDISKSPACE -l d
> >         }
> >
> > When I add the service to a host it runs but I get 'null' returned.
> What syntax do I
> > need to use in checkcommand.cfg in order to get this working
> correctly. I have tried
> > searching for other peoples checkcommand.cfg files on google but have
> not yet
> > found any.
> >
> > Many thanks for any help,
> > Jo
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at 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
>
>



-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Nagios-users mailing list
Nagios-users at 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