Hi Antony,
these hints are very important for me. I was now able to change my setup with
your hints and the configuration is synced to the satellite. I was also able to
setup everything needed to execute the basic checks. I identifed a problem in
the Icinga log with the firewall preventing the master to talk to the
satellite. This is all fixed now.
I have two problems left:
1) I am not sure where I should place the ping4/6 checks. I want the master to
ping all hosts with address/address6 entries. I tried to add these checks
inside the master zone folder. The checks show up in icingaweb2, but they are
not sheduled and still waiting.
2) When I shutdown Icinga on the satellite, the master will show nothing in
red. I understand that this is intended as of when the satellite comes up again
it might pass all queued data to the master. Nevertheless I like to know when a
satellite stops reporting, the Icinga process might have crashed if the rest of
the host is still up. Checks aren't executed then.
Regards
Volker
Viele Grüße
Volker
> Am 21.12.2016 um 00:06 schrieb Antony Stone
> <[email protected]>:
>
>> On Tuesday 20 December 2016 at 21:38:44, Volker Janzen wrote:
>>
>> I see. I just do not understand yet how new commands are added to a
>> satellite. There must be some binary or script on the satellite that needs
>> to be executed. Will this be configured on the master and/or satellite
>> with top-down?
>
> Here's a hint for *any* Icinga2 system as soon as you start using the Master
> -
> Satellite - Client hierarchy:
>
> - rename /etc/icinga2/conf.d to something like /etc/icinga2/conf.d.dist (it
> doesn't really matter what, just change its name)
>
> - create a new, empty /etc/icinga2/conf.d and leave it empty
>
> - do this on *every* machine in your network (Master, Satellite/s, Client/s -
> all of them)
>
> Then create one directory per Zone name under /etc/icinga2/zones.d and put
> all
> the configuration files (such as the Host definitions) which are specific to
> that
> Zone in there - you can name the files anything you like so long as they end
> in
> .conf
>
>
> Second hint - make sure all machines in your network have an entry in
> /etc/icinga2/zones.conf:
>
> object Zone "global-templates" { global = true }
>
> - then put any Service and ServiceCheck definitions (not Hosts) which apply
> to
> more than one Zone into files under /etc/icinga2/zones.d/global-templates
> (again, you can name these anything you like so long as they end in .conf)
>
> *That* is the way Icinga distributes top-down configurations to the
> Satellites
> and Clients.
>
>
> Hope that helps,
>
>
> Antony.
>
> --
> Users don't know what they want until they see what they get.
>
> Please reply to the list;
> please *don't* CC me.
> _______________________________________________
> 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
