Hi Steffen, I have no idea either. My test system works as expected, so I'm going to rebuild and see if that fixes it.
H On Mon, May 18, 2015 at 12:54 PM, Steffen Waitz <[email protected]> wrote: > Hi Henti, > > my solution is to move the host object out of zone.d into conf.d. But > this is not what I really wanted coz the Icinaga-master is now scheduling > and > the client is executing the checks. > I'd love to see that the clients are getting the config from the master and > doing the rest by them. Any ideas are highly welcome. > > Regards > Steffen > > Am Mittwoch, 13. Mai 2015, 09:59:20 schrieb Henti Smith: > > Hi Steffen, > > > > Did you come right with this ? > > > > I have the same problem and hoping you have a solution. > > > > Regards > > Henti > > > > On Thu, Apr 30, 2015 at 3:04 PM, Steffen Waitz <[email protected]> wrote: > > > Am Donnerstag, 30. April 2015, 14:14:08 schrieb Michael Friedrich: > > > > Am 30.04.2015 um 13:54 schrieb Steffen Waitz: > > > > > Dear list, > > > > > > > > > > I've more or less succesfully configured Icinga2 in a master - > > > > > > satellite > > > > > > > > environment. The sateliites are in their own zones and the config > is > > > > > pushed > > > > > from the master. Any remote checks are reported back to the master. > > > > > > > > > > Icinga2 created the hostobjects and added the services to it. But > > > > > when > > > > > I do a ifdown eth0 on the satellite the check hostalive will always > > > > > > report > > > > > > > > "UP". > > > > > > > > > > My master zone.conf looks like this: > > > > > > > > > > object Endpoint "client3" { > > > > > > > > > > host = "client3" > > > > > > > > > > } > > > > > > > > > > object Endpoint "icinga2" { > > > > > > > > > > host = "icinga2" > > > > > > > > > > } > > > > > > > > > > object Zone "client3" { > > > > > > > > > > parent = "icinga2" > > > > > endpoints = [ "client3" ] > > > > > > > > > > } > > > > > > > > > > object Zone "icinga2" { > > > > > > > > > > endpoints = [ "icinga2" ] > > > > > > > > > > } > > > > > > > > > > and on the satellite it looks like this: > > > > > > > > > > object Endpoint "client3" { } > > > > > > > > > > object Endpoint "icinga2" { } > > > > > > > > > > object Zone "icinga2" { > > > > > > > > > > endpoints = [ > > > > > > > > > > "icinga2" > > > > > > > > > > ] > > > > > > > > > > } > > > > > > > > > > object Zone "client3" { > > > > > > > > > > endpoints = [ > > > > > > > > > > "client3" > > > > > > > > > > ] > > > > > parent = "icinga2" > > > > > > > > > > } > > > > > > > > > > Is there something that I overlooked? I know I can add a service > check > > > > > > for > > > > > > > > the clusterzones but a working hostcheck would be nice. > > > > > > > > Then you probably should use the cluster check command for the host > as > > > > well, and ensure that this check is executed on the master, not the > > > > satellite. > > > > > > Well I did already, this is my host definition which is in > > > /etc/icinga2/zones.d/client3 as host.conf > > > > > > object Host "client3" { > > > > > > import "generic-host" > > > > > > address = "192.168.122.10" > > > > > > vars.remote_client = "client3" > > > vars.cluster_zone = vars.remote_client > > > > > > check_command = "cluster-zone" > > > > > > } > > > > > > But unfortunaly no success. How do I get the master to excecute the > > > hostcheck? > > > Moving the hostdefintion from zones.d to conf.d would break the idea > that > > > the > > > satellite will do the checks, right? > > > > > > Many thanks > > > Steffen > > > > > > > > > > > > > > > _______________________________________________ > > > icinga-users mailing list > > > [email protected] > > > https://lists.icinga.org/mailman/listinfo/icinga-users > > _______________________________________________ > icinga-users mailing list > [email protected] > https://lists.icinga.org/mailman/listinfo/icinga-users > -- --
_______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
