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"
}

object Endpoint "mon02.redacted.local" {
  host = "mon02.redacted.local"
}

object Endpoint "mon03.redacted.local" {
  host = "mon03.redacted.local"
}

object Zone "zone-master" {
  endpoints = [ "mon01.redacted.local" ]
}

object Zone "zone-lu" {
  endpoints = [ "mon02.redacted.local" ]
  parent = "zone-master"
}

object Zone "zone-aws" {
  endpoints = [ "mon03.redacted.local" ]
  parent = "zone-master"
}

object Zone "global-templates" {
  global = true
}
--------------% end snip %--------------


(affected) Satellite :

--------------% 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"
}

object Endpoint "mon02.redacted.local" {
  host = "mon02.redacted.local"
}

object Zone "zone-master" {
  endpoints = [ "mon01.redacted.local" ]
}

object Zone "zone-lu" {
  endpoints = [ "mon02.redacted.local" ]
  parent = "zone-master"
}

object Zone "global-templates" {
  global = true
}
--------------% end snip %--------------


api config on satellite:

--------------% snip %--------------
# cat /etc/icinga2/features-enabled/api.conf
/**
 * The API listener is used for distributed monitoring setups.
 */
object ApiListener "api" {
  cert_path = SysconfDir + "/icinga2/pki/" + NodeName + ".crt"
  key_path = SysconfDir + "/icinga2/pki/" + NodeName + ".key"
  ca_path = SysconfDir + "/icinga2/pki/ca.crt"

  accept_config = true
  accept_commands = true

  ticket_salt = TicketSalt
}
--------------% end snip %--------------


Communication works, I verified this on the master:

# date; icinga2 node list | grep mon02
Thu Mar 31 12:12:40 CEST 2016
Node 'mon02.redacted.local' (last seen: Thu Mar 31 12:12:13 2016)


This morning I noticed that the mon02 was lacking 30s behind timewise. I
corrected this but afterwards the configs still didn't get sent into the
zone.

When I reload the master, I notice the following log entry on the satellite:

[2016-03-31 12:16:11 +0200] notice/JsonRpcConnection: Received
'config::UpdateObject' message from 'mon01.redacted.local'
[2016-03-31 12:16:11 +0200] notice/ApiListener: Received update for object:
{"modified_attributes":{"enable_notifications":true},"name":"studio2-controller","original_attributes":["enable_notifications"],"type":"Host","version":1459419371.9411408901}
[2016-03-31 12:16:11 +0200] notice/ApiListener: Processing config update
for object 'studio2-controller': Object version 1.45942e+09 is older than
the received version 1.45942e+09.
[2016-03-31 12:16:11 +0200] notice/JsonRpcConnection: Received
'config::UpdateObject' message from 'mon01.redacted.local'
[2016-03-31 12:16:11 +0200] notice/ApiListener: Received update for object:
{"modified_attributes":{"enable_notifications":true},"name":"studio2-controller","original_attributes":["enable_notifications"],"type":"Host","version":1456323971.4780950546}
[2016-03-31 12:16:11 +0200] notice/ApiListener: Discarding config update
for object 'studio2-controller': Object version 1459419371.941141 is more
recent than the received version 1456323971.478095.
[2016-03-31 12:16:11 +0200] notice/JsonRpcConnection: Received
'config::UpdateObject' message from 'mon01.redacted.local'
[2016-03-31 12:16:11 +0200] notice/ApiListener: Received update for object:
{"modified_attributes":{"enable_notifications":true},"name":"app016!HTTPS","original_attributes":["enable_notifications"],"type":"Service","version":1459419371.9434659481}
[2016-03-31 12:16:11 +0200] notice/ApiListener: Processing config update
for object 'app016!HTTPS': Object version 1.45942e+09 is older than the
received version 1.45942e+09.
[2016-03-31 12:16:11 +0200] notice/JsonRpcConnection: Received
'config::UpdateObject' message from 'mon01.redacted.local'
[2016-03-31 12:16:11 +0200] notice/ApiListener: Received update for object:
{"modified_attributes":{"enable_notifications":true},"name":"app016!HTTPS","original_attributes":["enable_notifications"],"type":"Service","version":1456928284.5234920979}
[2016-03-31 12:16:11 +0200] notice/ApiListener: Discarding config update
for object 'app016!HTTPS': Object version 1459419371.943466 is more recent
than the received version 1456928284.523492.
[2016-03-31 12:16:11 +0200] notice/JsonRpcConnection: Received
'config::UpdateObject' message from 'mon01.redacted.local'
[2016-03-31 12:16:11 +0200] notice/ApiListener: Received update for object:
{"modified_attributes":{"enable_notifications":true},"name":"esxl001!Hardware","original_attributes":["enable_notifications"],"type":"Service","version":1459419371.9434959888}
[2016-03-31 12:16:11 +0200] notice/ApiListener: Processing config update
for object 'esxl001!Hardware': Object version 1.45942e+09 is older than the
received version 1.45942e+09.
[2016-03-31 12:16:11 +0200] notice/JsonRpcConnection: Received
'config::UpdateObject' message from 'mon01.redacted.local'

The messages "Object version ... is older than..." caught my eye. Could
they prevent a successful sync? Even for other config files unrelated to
these objects?

On Thu, Mar 31, 2016 at 10:13 AM, Michael Friedrich <
michael.friedr...@netways.de> wrote:

>
> > On 31 Mar 2016, at 10:01, Claudio Kuenzler <c...@claudiokuenzler.com>
> 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 that one too) the config file is not sent to the satellite endpoint
> of that zone.
>
> Please add the zones.conf from both nodes.
>
> Further please show the ApiListener config from inside
> features-enabled/api.conf on the satellite node.
>
> Even further please investigate on the troubleshooting docs with the
> cluster (config sync). (Debug) log entries, denied config updates, etc.
>
> Kind regards,
> Michael
>
>
>
> >
> > Both master and satellite are running 2.4.4.
> > _______________________________________________
> > icinga-users mailing list
> > icinga-users@lists.icinga.org
> > https://lists.icinga.org/mailman/listinfo/icinga-users
>
>
> --
> Michael Friedrich, DI (FH)
> Senior Developer
>
> NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
> Tel: +49 911 92885-0 | Fax: +49 911 92885-77
> CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
> http://www.netways.de | michael.friedr...@netways.de
>
> ** OSDC 2016 - April - netways.de/osdc **
> ** OSBConf 2016 - September - osbconf.org **
> _______________________________________________
> icinga-users mailing list
> icinga-users@lists.icinga.org
> https://lists.icinga.org/mailman/listinfo/icinga-users
>
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to