Windows Process monitoring Issue

[sreinhardt]

Just to verify since it doesn't seem very clear on the other posts, I may be reading this incorrectly too. Are you doing other nsclient checks on this machine that are working? A quick way to test if the port is open is below:

nmap [Host IP] -p 12489

[lmiltchev]

Run the following commands and show the output of them:

Code: Select all

./check_nt -H <host_IP> -s <password> -p 12489 -v CLIENTVERSION
./check_nt -H <host_IP> -s <password> -p 12489 -v PROCSTATE -l rtAgent941.exe *32 -d SHOWALL

[USPHNetAdmins]

I tried the command from the Nagios server and got "Exception processing request: Request contained arguments (not currently allowed, check the allow arguments option). I used the following command:
/usr/local/nagios/libexec/check_nrpe - H 172.16.10.51 -c CheckProcState -a ShowAll rtagent941.exe=started

I also tried the config file and once I restarted the nclient++ service, all the check failed on that server and not just the rtagent process I am trying to monitor. I did change the IP of the allowed server, but that did not make a difference.

[yancy]

USPHNetAdmins,

Run the config wizard using the "NRPE" wizards and choose windows. That will fix the issue of all checks not showing up by useing NRPE to monitor the host. (Also NRPE is better maintained)

In the [NRPE] setting of the config NSC.ini, make sure the following is set:

;# COMMAND ARGUMENT PROCESSING
; This option determines whether or not the NRPE daemon will allow clients to specify arguments to commands that are executed.
;allow_arguments=1

-Yancy

[USPHNetAdmins]

Yancy,

Here is what I did.

1.) I uninstalled the NSCLIENT++ from the server and reinstall the latest stable x64 version.
2.) I then checked the NSC.ini and found that it was set to 0 and not 1.
3.) I deleted the server from Nagios and added it back using the Windows Server Wizard which was updated to the latest version.
4.) All the other items are being monitored, but this one process still shows as "No data was received from host".

The only thing left to try is reboot the server, but I will have to schedule some off time for that as it is a production server.

[sreinhardt]

There are potentially many other issues, and rebooting it likely will have little to no effect. Again, are you able to scan the ports with nmap to be sure that they are open.

nmap -p 12489 [Hostname\IP]
nmap -p 5666 [Hostname\IP]

[USPHNetAdmins]

Yes, when I scan the ports with nmap, they are both open. As noted before, other processes being monitored on the same server work fine. It is just this one process.

[abrist]

Lets check a different procstate, one that we know the name of and that exists:

Code: Select all

./check_nt -H <host_IP> -s <password> -p 12489 -v PROCSTATE -l explorer.exe -d SHOWALL

What errors do you receive for the command above?