check_nt: Could not parse arguments

[Palle L Jensen]

Thanks for the help,

> the -l is not needed since it is in the check command

I also tried with and without the -l

 

Unfortunately did this not work either, any other suggestions?

 

 

Thanks,

Palle

 

  _____  

From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Anthony
Montibello
Sent: Tuesday, January 29, 2008 7:36 PM
To: narendran.neelamegam at wipro.com; palleje at gmail.com;
nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] check_nt: Could not parse arguments

 

Hi, 

 

To help clarify, -s is for the password while $ARG1$ was missing from the
orriginal command causing the missing ARGUMENT error

THe Hostname is needed since the plugin does not know what host it is
without that.

the port in this case is needed since check_nt.c compiles with the default
port of 1248

the -l is not needed since it is in the check command

 

define command{
        command_name    check_nt_cpu
$USER1$/check_nt -H $HOSTADDRESS$ -p 12489 -s $USER7$  $ARG1$
}

 

define service{
       use                  generic-service
       host_name            host001
       service_description  CPU load
       servicegroups        load
       check_command        check_nt_cpu!CPULOAD!-l 5,80,90
       }

 

Tony (Author of NC_NEt)

 

 

On Jan 29, 2008 2:51 PM, <narendran.neelamegam at wipro.com> wrote:

 

Should your command be

 

$USER1$/check_nt -H $HOSTADDRESS$ -p 12489 -v CPULOAD -l $ARG1$

 

check_nt -H $HOSTADDRESS$ -p 12489 -s $USER7$

 

  _____  

From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Palle L
Jensen
Sent: Tuesday, January 29, 2008 10:32 PM
To: Nagios Users
Subject: [Nagios-users] check_nt: Could not parse arguments

 

Morning all,

 

I am having an issue with adding cpuload monitoring on windows machines.

I know there are no issues on the windows side since I have other services
being monitored with no problems.

Also the error message tells me the arguments that are specified are not
correct.

I have google'd, and checked the Nagios documentation and tried different
ways, but non works.

And this is were I am at now. Could anyone look this over and tell me what
is wrong?

- Error: check_nt: Could not parse arguments

 

- Check command definition:

 

define command{

        command_name    check_nt_cpu

        command_line    $USER1$/check_nt -H $HOSTADDRESS$ -p 12489 -s
$USER7$

 

 

- Service definition:

 

define service{

       use                  generic-service

       host_name            host001

       service_description  CPU load

       servicegroups        load

       check_command        check_nt_cpu!CPULOAD! -l 5,80,90

       }


Thanks,

Palle

 

 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080130/97b67dc7/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- next part --------------
_______________________________________________
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