Adding external Hosts

[jdalrymple]

Sorry that you had so much trouble, sounds like you're using the nsca_client module in nsclient? Did you get your result from your 2nd host or are you still waiting on that? If you're still having issues please sanitize and post your nsclient.ini file from any hosts giving you trouble - sometimes a fresh set of eyes on a problem can be helpful.

[skahlam]

It is the same nsclient.ini file that is working on Host1. I copied it over to the nsclient++ install on Host2
Host2 is a Hyper-v vm on Host1
Host1 is working, Host2 is not.
This is the scenario I will have most often and will need to get working.
The nagios tech told me to enable and install all modules of NSCP-0.4.1.105-x64.msi
It is installed on Host1 exactly as it is installed on Host2

[jdalrymple]

The only reason that wouldn't work in my mind is if nsca wasn't accepting checks for that host. This could be because of "only_from" in your xinetd config or because of your system's firewall. Did you verify those 2 spots?

Mind you, the host will show up in unconfirmed objects, not in host details, etc.

[skahlam]

The only from was commented out by the Nagios tech I worked with.
I can check again.

[skahlam]

Yes it is commented out. The nsclient.log on Host1 that is working shows this:
2015-06-11 12:46:15: e:..\..\..\..\nscp\modules\NSCAClient\NSCAClient.cpp:447: Error: Failed to connect to: :5667 :No connection could be made because the target machine actively refused it
So NSCA is not working on this host but this host is in fact returning passive checks using some module.
That same error exists on Host2 as well.

[jdalrymple]

OK,

Again, sorry for your frustration. Like I said, generally speaking straight copying the config across should work for a passive check. I guess a couple other things to think about:

1) Did you also copy across any external scripts that the passive checks call?
2) Did you restart NSCP after copying the config?

[skahlam]

Yes restarted nsclient service and no external scripts involved.

[jdalrymple]

I'm afraid I'm at a loss then. If you can post your nsclient.ini file it might reveal something.

The other thing you could do is look at your nscp debug log (if it exists) at c:\program files\nsclient++\nsclient.log - if it doesn't exist add these lines to nsclient.ini and restart:

Code: Select all

[/settings/log]
file name = nsclient.log
level = debug