Page 1 of 1
[check_winprocess.pl] Configuration Help
Posted: Mon Apr 20, 2015 1:31 pm
by sh.shekhar89
Hi All,
I am trying to configure to check a process memory utilization and cpu utilization using check_winprocess.pl (
https://www.itefix.net/check_winprocess)
Can some one guide me how to configure?? I have copied the .pl files in nagios folder and .exe file in windows ns client script folder. but when i am running the command on nagios server , i am getting this below error :
[root@test libexec]# ./check_nrpe -H 192.168.199.1 -c check_proc_cnt
No handler for command: check_proc_cnt
can some one guide me??
Re: [check_winprocess.pl] Configuration Help
Posted: Mon Apr 20, 2015 3:04 pm
by jolson
It does not look like the plugin 'check_winprocess.exe' includes an NRPE listener, unless I'm missing something. You need an NRPE listener to accept incoming connections from your Nagios server. A few popular plugins that can listen for NRPE are as follows:
http://www.nsclient.org/
http://exchange.nagios.org/directory/Ad ... PA/details
I personally like NCPA, but NSClient is a very respected application as well. I recommend researching them both, and testing to see which one you prefer.
Please let us know if you have any questions. Thanks!
Re: [check_winprocess.pl] Configuration Help
Posted: Wed Apr 22, 2015 2:52 pm
by sh.shekhar89
jolson wrote:It does not look like the plugin 'check_winprocess.exe' includes an NRPE listener, unless I'm missing something. You need an NRPE listener to accept incoming connections from your Nagios server. A few popular plugins that can listen for NRPE are as follows:
http://www.nsclient.org/
http://exchange.nagios.org/directory/Ad ... PA/details
I personally like NCPA, but NSClient is a very respected application as well. I recommend researching them both, and testing to see which one you prefer.
Please let us know if you have any questions. Thanks!
Hello jolson,
But i have seen many people are using this plugin to check the process memory.
Can anyone help me in configuring this plugin??
Re: [check_winprocess.pl] Configuration Help
Posted: Wed Apr 22, 2015 3:38 pm
by jolson
What version of NSClient are you running?
Do any other checks work?
Could you please post your nsc.ini file? I would like to take a look at it to ensure that NSClient is properly configured for this plugin.
Re: [check_winprocess.pl] Configuration Help
Posted: Wed Apr 22, 2015 3:48 pm
by sh.shekhar89
jolson wrote:What version of NSClient are you running?
Do any other checks work?
Could you please post your nsc.ini file? I would like to take a look at it to ensure that NSClient is properly configured for this plugin.
i am using 0.4.1.73, i have attached nsc.ini file.
Re: [check_winprocess.pl] Configuration Help
Posted: Wed Apr 22, 2015 4:08 pm
by jolson
Did you restart NSClient on the Windows machine you're trying to monitor?
From an administrator command prompt:
Then retry your NRPE check from Nagios.
If that does not work, please stop NSClient and enable test mode:
Code: Select all
net stop nscp
cd "C:\Program Files\NSClient++"
nscp.exe test
Then retry your check - what errors are you getting in the terminal?
Let me know what you find out.
Re: [check_winprocess.pl] Configuration Help
Posted: Thu Apr 23, 2015 9:40 am
by sh.shekhar89
jolson wrote:Did you restart NSClient on the Windows machine you're trying to monitor?
From an administrator command prompt:
Then retry your NRPE check from Nagios.
If that does not work, please stop NSClient and enable test mode:
Code: Select all
net stop nscp
cd "C:\Program Files\NSClient++"
nscp.exe test
Then retry your check - what errors are you getting in the terminal?
Let me know what you find out.
This is the output i am getting when i am running the above command
Re: [check_winprocess.pl] Configuration Help
Posted: Thu Apr 23, 2015 1:19 pm
by jolson
Do any other NRPE checks work?
Everything looks good as far as I can tell.
It doesn't look like there's any 'test' input - meaning the listener didn't receive any data. Otherwise we would see errors - make sure that port 5666 is accessible through your Windows Firewall.