check_nt and CRITICAL and WARNING states problem

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
piotrusx
Posts: 3
Joined: Mon Jan 04, 2016 7:13 am

check_nt and CRITICAL and WARNING states problem

Post by piotrusx »

Hello,
I try use:

Code: Select all

/usr/local/nagios/libexec/check_nt -H 192.168.129.3 -v USEDDISKSPACE -s xyz -l g -w 90 -c 98 -p 12489
but "w" and "c" variables don't work.
Nagios always sets 80% for state WARNING.
How fix it and to change for own values?
Could help me?

Peter.
User avatar
mcapra
Posts: 3739
Joined: Thu May 05, 2016 3:54 pm

Re: check_nt and CRITICAL and WARNING states problem

Post by mcapra »

Which version of NSClient++ is the remote machine running?

Can you run that check command from the CLI and share the full output?

Code: Select all

/usr/local/nagios/libexec/check_nt -H 192.168.129.3 -v USEDDISKSPACE -s xyz -l g -w 90 -c 98 -p 12489
Former Nagios employee
https://www.mcapra.com/
piotrusx
Posts: 3
Joined: Mon Jan 04, 2016 7:13 am

Re: check_nt and CRITICAL and WARNING states problem

Post by piotrusx »

Hi.
I use NSClient++ version 0.4.3.143.

I can't use nagios-cli because I have hosts names with space and I receive an error when I try do it:
nagios > host MPDOK DB gw2_biurowa
Syntax error: host takes at most 1 argument (3 given)
Without spaces it works.
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: check_nt and CRITICAL and WARNING states problem

Post by rkennedy »

I don't think resolvable hostnames can have a space in them, could you try using an IP address in the command @mcapra mentioned?
Former Nagios Employee
Locked