Anyone else having problem with 2.4.4 and the sync of config files to the
satellite servers?
I created a new config file within /etc/icinga2/zones.d/zone-1/hosts/APP/
and after reload (and restart, tested that one too) the config file is not
sent to the satellite endpoint of that zone.
Both master
> On 31 Mar 2016, at 10:01, Claudio Kuenzler wrote:
>
> Anyone else having problem with 2.4.4 and the sync of config files to the
> satellite servers?
No, not that I know of.
> I created a new config file within /etc/icinga2/zones.d/zone-1/hosts/APP/ and
> after reload (and restart, tested th
> On 30 Mar 2016, at 12:36, Christian Moreno Moreno
> wrote:
>
> Hi,
>
> We have 2 Zones with 3 Endpoints in our icinga2:
>
> object Endpoint "icinga-01" {
> host = ""
> port = 5665
> }
>
> object Endpoint "icinga-02" {
> host = ""
> port = 5665
> }
>
> object Endpoint "icinga-03
Hi Michael,
Master:
--% snip %--
# cat /etc/icinga2/zones.conf
/*
* Endpoint and Zone configuration for a cluster setup
* This local example requires `NodeName` defined in
* constants.conf.
*/
object Endpoint "mon01.redacted.local" {
host = "mon01.redacted.local"
}
hc4cfahme2htx4w2eo3ekl0io4anj...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Anyone else having problem with 2.4.4 and the sync of config files to the
> satellite servers?
> I created a new config file within /etc/icinga2/zones.d/zone-1/hosts/APP/
>
This should now be fixed in current master. Even without host property
it would now work fine unless your Endpoint name can be resolved to a
reachable IP address.
Cheers,
Thomas
Am 29.03.2016 um 17:48 schrieb Zachary McGibbon:
> Thanks, this worked in my zones.conf
>
> object Endpoint NodeName {
I continued testing and only the mon02 satellite is having this problem.
mon03 satellite server for the zone "zone-aws" is working fine. mon03 is
also running with 2.4.4.
On mon02 nothing gets updated anymore (even existing and previously working
objects).
Unfortunately there are no errors (besides
