NSClient++ Help (#1) - A total novice needs help - NSClient++ Version Critical (#931) - Message List
Hi everyone
I've been thrown in at the deep end at work and I'm desperate for some quickfire help as I just don't have time to research. I'm hoping someone will oblige....
I have NSClient++ (x64) v0.3 installed on 2 Windows Server 2008 R2 boxes. Nagios is setup to monitor the boxes but for some reason they are sending a Critical alert relating to the NSClient++ Version. And I presume its because of this that all the other checks are in Critical status as well with the Connections being refused or Sockets timing out after 30secs. Apart from Ping actually which is OK. I just don't understand what the problem can be because there are other servers being monitored with exactly the same configuration and they are working fine.
Needless to say, what I really need is a step-by-step checklist of what to do if anyone would be kind enough.
Hopefully hear from someone soon!
Cheers Nick
-
Message #2447
How do you monitor them? Which command, which protocol, etc etc...
But I would start by not diagnosing errors from "Nagios". Nagios will make it much much harder to diagnose your problem. Best place to start is:
- Local from NSCLient++
- From nagios-server command line
3, From nagios UI.
Doing it the other way around will only take much longer and be much more difficult...
I think it is also important to understand that "green and red" are not really useful when diagnosing errors. You need to understand which command "did not work" so you can replicate them and understand why...
Michael Medin
mickem03/17/12 11:28:55 (15 months ago) -
Message #2470
try nsclient++ /test and see what happens when your server contacts the box, maybe its an invalid machine name? ... typos can be ugly ;)
soop03/22/12 13:50:09 (15 months ago)
