Page 1 of 1
check_nt and CRITICAL and WARNING states problem
Posted: Fri Dec 09, 2016 9:00 am
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.
Re: check_nt and CRITICAL and WARNING states problem
Posted: Fri Dec 09, 2016 1:25 pm
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
Re: check_nt and CRITICAL and WARNING states problem
Posted: Sat Dec 10, 2016 12:24 pm
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.
Re: check_nt and CRITICAL and WARNING states problem
Posted: Mon Dec 12, 2016 10:59 am
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?