On Wed, 28 Nov 2012, Olivier Cortambert wrote:

> However, I still don't see anything in the icinga.log about
> these messages. So I am guessing that I am missing the
> communication between nsca and Icinga.

    Make sure that your "command_file" declaration in nsca.cfg
is pointing to the same "external command file" that Icinga
uses and that the processes are running with proper permission
to write to that file.  You also might want to set the
"alternate_dump_file" declaration to another file that can
be written into if the main command file is unavailable for
any reason (including permissions); that can be useful for
troubleshooting.

> I also haven't yet added the host in the icinga configuration
> of the central instance, as I am wondering how to tell icinga
> that these hosts are monitored by another service. What is the
> option, to tell icinga to accept passive host for these hosts
> and not do anything?

    You must have the hosts/services that are being run actively
on the "satellite" defined in the "central" instance.  Look into
the "active_checks_enabled" and "passive_checks_enabled" in the
object configuration doco; you will find hints in there.  The basic
premise in a distributed setup is to have the services on the
aggregator host (your "central" system) only accept passive
checks (active_checks_enabled 0) for things that are actively
checked on the monitoring hosts (your "satellite" host).  Note that
you will probably want to look into "freshness checking" once you
get the basics working, but worry about the basics first.

    Cheers!

+------------------------------------------------+---------------------+
| Carl Richard Friend (UNIX Sysadmin)            | West Boylston       |
| Minicomputer Collector / Enthusiast            | Massachusetts, USA  |
| mailto:crfri...@rcn.com                        +---------------------+
| http://users.rcn.com/crfriend/museum           | ICBM: 42:22N 71:47W |
+------------------------------------------------+---------------------+

------------------------------------------------------------------------------
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users

Reply via email to