Nagios Support Forum

Please help with getting NRPE checks working against Windows hosts (no success to date)

Using test case with "Could not construct return packet in NRPE handler check client side (nsclient.log) logs.." results.
Please point to the reliable list of performance checks that could be done against windows (and Linux) hosts

Can you please post your nsclient.ini / nsc.ini with any sensitive information excluded? You can find a lot of plugins for Windows, I am not sure what kind of list you are looking for. Here are some, for example: https://exchange.nagios.org/directory/P ... ndows-NRPE

hsmith wrote:Can you please post your nsclient.ini / nsc.ini with any sensitive information excluded? You can find a lot of plugins for Windows, I am not sure what kind of list you are looking for. Here are some, for example: https://exchange.nagios.org/directory/P ... ndows-NRPE

file added.

Log shows this error:
2015-11-24 11:40:27: error:modules\NRPEListener\NRPEListener.cpp:422: Request contained arguments (not currently allowed, check the allow_arguments option).
2015-11-24 11:40:27: error:modules\NRPEListener\NRPEListener.cpp:320: Exception handling NRPE packet
- even so I believed I have enabled arguments.

These are the commands I am trying to run:
check_nrpe!nagiosxi40!CheckCPU -a warn=80 crit=90 time=1m time=5m time=15m!!!!!!
check_nrpe!nagiosxi40!CheckCounter -a 'Counter=\Processor(0)\% Processor Time' ShowAll MaxWarn=80 MaxCrit=90!!!!!!

Maybe I am missing plugins or do not understand relationship in between NRPE and plugins?

Your NSC.ini wrote: allow_arguments=0
;NRPEClient.dll
allowed_hosts=10.x.x.x

;# ALLOWED HOST ADDRESSES
; This is a comma-delimited list of IP address of hosts that are allowed to talk to the all daemons.
; If leave this blank anyone can access the deamon remotly (NSClient still requires a valid password).
; The syntax is host or ip/mask so 192.168.0.0/24 will allow anyone on that subnet access
;allowed_hosts=127.0.0.1/32

These are a few of the configuration errors that jump out at me.

Uncomment NRPEClient.dll
Change allowed_hosts in multiple locations to the proper syntax that I quoted above. 10.0.0.0/8 if that's what you want to allow.
allow_arguments is set to 0 there. You need to set it to 1.

It seems like you're using a pretty outdated version. Any possibility of an upgrade?

hsmith wrote:

Your NSC.ini wrote: allow_arguments=0
;NRPEClient.dll
allowed_hosts=10.x.x.x

;# ALLOWED HOST ADDRESSES
; This is a comma-delimited list of IP address of hosts that are allowed to talk to the all daemons.
; If leave this blank anyone can access the deamon remotly (NSClient still requires a valid password).
; The syntax is host or ip/mask so 192.168.0.0/24 will allow anyone on that subnet access
;allowed_hosts=127.0.0.1/32

These are a few of the configuration errors that jump out at me.

Uncomment NRPEClient.dll
Change allowed_hosts in multiple locations to the proper syntax that I quoted above. 10.0.0.0/8 if that's what you want to allow.
allow_arguments is set to 0 there. You need to set it to 1.

It seems like you're using a pretty outdated version. Any possibility of an upgrade?

Made changes, thank you! (missed some things, too many "allowed_hosts"
- UNKNOWN: No handler for that command

Running NSClient 0.3.9, recommended by Nagios XI interface as stable VS newer version which is not stable(?)
- NRPE client stated as Beta in comment / does it mean that "unstable" NSClient has more up to date version? - but should I install one?

I've had good luck with 0.4.3.143

Are you able to run a check_nrpe -H x.x.x.x against that host yet?

hsmith wrote:I've had good luck with 0.4.3.143

Are you able to run a check_nrpe -H x.x.x.x against that host yet?

login as: root
[email protected]'s password:
Last login: Tue Nov 24 12:07:16 2015
[root@fikc-nagxidev01 ~]# nmap 10.67.0.91 -p 5666

Starting Nmap 6.47 ( http://nmap.org ) at 2015-11-24 12:15 EST
Nmap scan report for 10.67.0.91
Host is up (0.14s latency).
PORT STATE SERVICE
5666/tcp open nrpe

Nmap done: 1 IP address (1 host up) scanned in 0.38 seconds
You have new mail in /var/spool/mail/root
[root@fikc-nagxidev01 ~]# /usr/local/nagios/libexec/check_nrpe -H 10.67.0.91
NRPE v2.15



[root@fikc-nagxidev01 ~]# /usr/local/nagios/libexec/check_nrpe -H 10.x.x.65
I (0.3.9.328 2011-08-16) seem to be doing fine...

NRPE seem to respond. In terms of client what is the difference and should we use the new one (stability is very important)?

To be completely honest, I think both versions are pretty stable. I wouldn't recommend upgrading to the beta of his new version at the moment. In my opinion, the configuration is much cleaner in the newer versions. For now, since this one is able to communicate, we should probably just stick with it. What would you like to configure/troubleshoot next regarding this?

hsmith wrote:To be completely honest, I think both versions are pretty stable. I wouldn't recommend upgrading to the beta of his new version at the moment. In my opinion, the configuration is much cleaner in the newer versions. For now, since this one is able to communicate, we should probably just stick with it. What would you like to configure/troubleshoot next regarding this?

I was trying to use this site for NRPE performance checks: http://sites.box293.com/nagios/guides/c ... s/cpu-load

Please clarify if I have to run plugins in conjunction with NRPE or NRPE is enough (would version of NRPE be important in this case?)

dlukinski wrote:I was trying to use this site for NRPE performance checks: http://sites.box293.com/nagios/guides/c ... s/cpu-load

His guide is good. I recommend it.

dlukinski wrote:Please clarify if I have to run plugins in conjunction with NRPE or NRPE is enough (would version of NRPE be important in this case?)

NRPE version is not that important right now. You CAN run plugins with NRPE, which will greatly expand the functionality of it. Can you try to CPU check now that we have the nsc cleaned up a little?