Page 1 of 1
Check_nt returning Warning instead of CRITICAL
Posted: Tue Oct 25, 2016 11:42 am
by vtadisina
I am using nsclient on a windows server and trying to get the status of a process on the server using check_nt. I want check_nt to return CRITICAL when the process is not running on the server instead it is returning Warning. Is there something that I have to specify in the command line to report it as CRITICAL. This is the command that I am using
Code: Select all
check_nt -H xx.xx.xx.xx -s xxxxx -p 12489 -v PROCSTATE -l xxxxxxxx.exe -d SHOWALL
Re: Check_nt returning Warning instead of CRITICAL
Posted: Tue Oct 25, 2016 1:28 pm
by dwhitfield
What version of NSClient are you using? I know in some cases upgrading to NSCP-0.4.1.90-x64 has fixed similar issues. That said, There are some pretty serious bugs in 4.3, so I would suggest 4.4 or higher. Of course, if you are already using a newer version, we will have to dig a little deeper.
Re: Check_nt returning Warning instead of CRITICAL
Posted: Wed Oct 26, 2016 9:35 am
by vtadisina
I am using 0.4.1. I'll upgrade to 4.4 and see if that works.
Re: Check_nt returning Warning instead of CRITICAL
Posted: Wed Oct 26, 2016 9:43 am
by dwhitfield
Great, let us know how it goes.
Re: Check_nt returning Warning instead of CRITICAL
Posted: Wed Oct 26, 2016 12:03 pm
by vtadisina
I installed 0.50 but port 12489 connection refused. I tried to open the port but its not working. what can i do?
Re: Check_nt returning Warning instead of CRITICAL
Posted: Wed Oct 26, 2016 12:21 pm
by dwhitfield
on both the server and the client run nmap on that port and give the output. Do that locally if you are not your network admin (else you might get a call from your network admin).
Once we know where it's closed, we can work on opening it up.