On one of the windows servers, NSClinet is in OK state but the following status information is showing
NSClient is running. Version is could not fetch information from server
Other services are in warning and unknown state
Memory Physical Unknown CHECK_NRPE: Receive header underflow - only 0 bytes received (4 expected).
NT-CPU Warning could not fetch information from server
NT-DriveC Warning could not fetch information from server
Apart from this no other services are configured on this server.
[root@nagios server libexec]# ./check_nrpe -H 10.215.50.24
CHECK_NRPE: Receive header underflow - only 0 bytes received (4 expected).
What could be the problem.
NSClient is running. Version is could not fetch information
Re: NSClient is running. Version is could not fetch informat
Could you please help me on this.
Re: NSClient is running. Version is could not fetch informat
I have this same issue with one of my servers as well.
Accidentally deleted the old NS Client++ and now the new version(even when legacy mode is checked) states "____Warning: Could not fetch information from server"(Yellow) with the occasional "____Usage unknown: Could not fetch information from server"(Orange)
Accidentally deleted the old NS Client++ and now the new version(even when legacy mode is checked) states "____Warning: Could not fetch information from server"(Yellow) with the occasional "____Usage unknown: Could not fetch information from server"(Orange)
Re: NSClient is running. Version is could not fetch informat
NSClient++ has a log fiile located 'C:\Program Files\NSClient++\nsclient.log'
The NSClient log level defaults to "info" if I remember correctly. You can kick this up to debug in the nsclient.ini file and tail the logs (I use NotePad++ for this on windows) to see if you can find what's actually generating the error.
*NOTE*
This will generate a lot of log entries, only leave the settings at debug while you are actually debugging!
That being said you should have a look at NCPA
The NSClient log level defaults to "info" if I remember correctly. You can kick this up to debug in the nsclient.ini file and tail the logs (I use NotePad++ for this on windows) to see if you can find what's actually generating the error.
*NOTE*
This will generate a lot of log entries, only leave the settings at debug while you are actually debugging!
That being said you should have a look at NCPA