Plugins Helps

[Box293]

Can you please upload the nsclient.ini file from the XP machine.

[kwhogster]

OK

I attached the nsiclient.ini

[rkennedy]

Box293

Great catch on the service name that worked making the changes now.


The NSCLIENT version of 32 bit is

NSCP-0.4.3.143

I ran this on all machines

Type cd "\Program Files\NSClient++\" and press Enter
?Type nscp settings --activate-module NRPEServer --add-defaults and press Enter

nscp settings --activate-module NRPEServer --add-defaults

?This may prompt you for permission
?Type nscp settings --path /settings/NRPE/server --key "allow arguments" --set true and press Enter

nscp settings --path /settings/NRPE/server --key "allow arguments" --set true

?This may prompt you for permission
?Type nscp settings --path /settings/NRPE/server --key "allow nasty characters" --set true and press Enter

nscp settings --path /settings/NRPE/server --key "allow nasty characters" --set true

?This may prompt you for permission

?IF this is NSClient++ 0.4.3 onwards

?Type nscp settings --path /settings/NRPE/server --key insecure --set true and press Enter

nscp settings --path /settings/NRPE/server --key insecure --set true

?This may prompt you for permission

net stop nscp

net start nscp

All 64 bit clients are NSCP 0.4.1.73


I ran this on the 32 bit computers

?IF this is NSClient++ 0.4.3 onwards

?Type nscp settings --path /settings/NRPE/server --key insecure --set true and press Enter

nscp settings --path /settings/NRPE/server --key insecure --set true


Thoughts

NSClient++ can be finicky through the CLI, but it looks like your allow arguments, insecure mode, and allow nasty characters are all true now. What issue are you currently experiencing?

[kwhogster]

My original post was this

After adding on my computers to this all worked except for two of them both of them are 32 bit computers one is Windows XP Pro the other is Windows 2003 Server

Get this error CHECK_NRPE: Error - Could not complete SSL handshake.


Does NRPE work with 32 bit computers?

[tgriep]

I haven't used the 32 bit version of the client but is should work.

I do see a few changes to the nsclient.ini file that should work for you.
Edit that file and under this section

Code: Select all

[/settings/NRPE/server]

Remove these 2 lines

Code: Select all

verify mode = peer-cert
use ssl = true

Save the file and restart the NSClient++ service and see if that fixes it for you.

[kwhogster]

Removed these
verify mode = peer-cert
use ssl = true

Now I get this

root@TGCS017:/usr/lib/nagios/plugins# ./check_nrpe -H 10.2.8.75 -t 30 -c CheckDriveSize -a ShowAll=long MinWarn =20% MinCrit=10% Drive=C: perf-unit=G
CHECK_NRPE: Invalid packet type received from server.

[tgriep]

Try changing this from

Code: Select all

ssl options = no-sslv2,no-sslv3

to

Code: Select all

ssl options =

Save and restart like before.

If you get an error, can you upload the nsclient.log file from that windows host?

[kwhogster]

same error

root@tgcs017:/usr/lib/nagios/plugins# ./check_nrpe -H 10.2.8.75 -t 30 -c CheckDriveSize -a ShowAll=long MinWarn =20% MinCrit=10% Drive=C: perf-unit=G
CHECK_NRPE: Invalid packet type received from server.

[Box293]

Can you stop the NSClient++ service
Open a command prompt
type:

Code: Select all

cd "\Program Files\NSClient++\"
nscp test

What output is produced?

[kwhogster]

boz293

ran net stop nscp

nscp test >>c:\nscp.txt

See attached