NSClient++ Help (#1) - NSClient reporting incorrect server statuses (#956) - Message List
3 of my 10+ servers are sending incorrect information to Nagios through NSClient++. They are all sending that their CPU Load, Memory Usage, and Uptime all have 'Critical' statuses, even though when I go into these servers, they are perfectly fine and none of these statuses are true. Now the strange thing is, when I run the NSClient++ test DOS script, they report correct information and these problems disappear, until the next scheduled check, where they once again send the wrong information.
Anyone got ideas?
Thanks
-
Message #2534
Could you provide some more details?
- Which version of nsclient++?
- Which command fails?
- Does nsclient++ log say anything when it is wrong?
- What is the error message that comes with critical?
- ...
Michael Medin
mickem04/14/12 06:40:34 (13 months ago)-
Message #2541
The three servers with the problems are running 0.3.9 (2 running 64bit, 1 running 32bit). All three servers are reported as having critical CPU Loads, Memory Usage, and Uptime. One of the three also reports as having Critical C:\ Drive Space. The status information section reads: "CRITICAL - Socket timeout after 20 seconds" When I log on to these servers, none of these 'critical problems' are actually true and they all are running normally. I tried going into each of their nsclient++ configurations to see if the IP field was incorrect or something along those lines, but all the information seemed correct.
peterb904/16/12 22:18:46 (13 months ago)-
Message #2542
Socket timeout means it failed to read data from the network. Could be miss configuration, ssl mismatch, as well as firewall and network issues... Best way is to start nsclient++ in test mode and work your way backwards ie (there is a guide for doing this in the guides section so read that...)
Michael Medin
mickem04/17/12 07:25:36 (13 months ago)
-
