NSClient is running. Version is could not fetch information

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.
Locked
Pratapa
Posts: 150
Joined: Tue Oct 01, 2019 1:33 am

NSClient is running. Version is could not fetch information

Post by Pratapa »

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.
Pratapa
Posts: 150
Joined: Tue Oct 01, 2019 1:33 am

Re: NSClient is running. Version is could not fetch informat

Post by Pratapa »

Could you please help me on this.
majoradhd
Posts: 7
Joined: Wed Feb 05, 2020 7:23 pm

Re: NSClient is running. Version is could not fetch informat

Post by majoradhd »

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)
snapier3
Posts: 144
Joined: Tue Apr 23, 2019 7:12 pm

Re: NSClient is running. Version is could not fetch informat

Post by snapier3 »

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 ;)
Locked