Check_nt returning Warning instead of CRITICAL

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
vtadisina
Posts: 28
Joined: Thu Sep 29, 2016 9:39 am

Check_nt returning Warning instead of CRITICAL

Post 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
dwhitfield
Former Nagios Staff
Posts: 4583
Joined: Wed Sep 21, 2016 10:29 am
Location: NoLo, Minneapolis, MN
Contact:

Re: Check_nt returning Warning instead of CRITICAL

Post 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.
vtadisina
Posts: 28
Joined: Thu Sep 29, 2016 9:39 am

Re: Check_nt returning Warning instead of CRITICAL

Post by vtadisina »

I am using 0.4.1. I'll upgrade to 4.4 and see if that works.
dwhitfield
Former Nagios Staff
Posts: 4583
Joined: Wed Sep 21, 2016 10:29 am
Location: NoLo, Minneapolis, MN
Contact:

Re: Check_nt returning Warning instead of CRITICAL

Post by dwhitfield »

Great, let us know how it goes.
vtadisina
Posts: 28
Joined: Thu Sep 29, 2016 9:39 am

Re: Check_nt returning Warning instead of CRITICAL

Post 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?
dwhitfield
Former Nagios Staff
Posts: 4583
Joined: Wed Sep 21, 2016 10:29 am
Location: NoLo, Minneapolis, MN
Contact:

Re: Check_nt returning Warning instead of CRITICAL

Post 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.
Locked