Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
define service {
host_name TGCS010
service_description Check All Service
check_command check_nrpe!checkservicestate! -a CheckAll
servicegroups AllServices
check_interval 1
use generic-service
}
That works great the NSclient is 4.1.73 This is a Windows 2008 64 bit server
define service {
host_name TGCS002
service_description Check All Service
check_command check_nrpe!check_service! -a CheckAll "filter=name not like 'clr_optimization_v4.0.30319'" exclude=SysmonLog
servicegroups AllServices
check_interval 1
use generic-service
}
This one give me ---- CHECK_NRPE: Invalid packet type received from server.
The nsclient is 4.3.143 it is a Windows 2003 32 Bit Server
I have Windows 2012 Servers and other Windows 2008 servers all working and all on NSclient 4.1.73
Are you able to test your install with NSClient++ 4.1.73 on the failing machine, and let us know if that works successfully? This sounds like more of a NSClient++ compatibility issue if it's working fine on other machines.
NSClient++ is not one of our products. I would recommend contacting the developer, and/or posting your questions on the NSClient++ support forum. They may be able to resolve your issue faster. I found the same (or similar) issue reported on their forum:
that is for 4.3 I am using 4.1
do not think it applies
My impression was that you were having this issue with NSClient++ 4.3.143, and NSClient++ 4.1.73 was working fine... You said:
This one give me ---- CHECK_NRPE: Invalid packet type received from server. The nsclient is 4.3.143 it is a Windows 2003 32 Bit Server
I have Windows 2012 Servers and other Windows 2008 servers all working and all on NSclient 4.1.73
kwhogster wrote:so why am I getting invalid packet received from server?
This check works on all other computers
Exactly what was previously stated. We are working with the information you provided to us. It might work on other computers, but it isn't Nagios related at this point. The issue is the different versions of NSClient++. We do not have control of what is fixed when, and what problems may arise with x version.