[2019-10-18 08:38:45 +0200] information/ApiListener: New client connection for identity 'mon1.site1.em.lan' from [192.168.53.211]:49114
[2019-10-18 08:38:45 +0200] information/ApiListener: Sending config updates for endpoint 'mon1.site1.em.lan' in zone 'site1.em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Finished sending config file updates for endpoint 'mon1.site1.em.lan' in zone 'site1.em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Syncing runtime objects to endpoint 'mon1.site1.em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Finished syncing runtime objects to endpoint 'mon1.site1.em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Finished sending runtime config updates for endpoint 'mon1.site1.em.lan' in zone 'site1.em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Sending replay log for endpoint 'mon1.site1.em.lan' in zone 'site1.em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Finished sending replay log for endpoint 'mon1.site1.em.lan' in zone 'site1.em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Finished syncing endpoint 'mon1.site1.em.lan' in zone 'site1.em.lan'.
[2019-10-18 08:38:45 +0200] information/JsonRpcConnection: Received certificate request for CN 'mon1.site1.em.lan' signed by our CA.
[2019-10-18 08:38:45 +0200] information/JsonRpcConnection: The certificate for CN 'mon1.site1.em.lan' is valid and uptodate. Skipping automated renewal.
icinga2.log satellite:
[2019-10-18 08:38:45 +0200] information/ApiListener: Reconnecting to endpoint 'main.em.lan' via host '192.168.53.210' and port '5665'
[2019-10-18 08:38:45 +0200] information/ApiListener: New client connection for identity 'main.em.lan' to [192.168.53.210]:5665
[2019-10-18 08:38:45 +0200] information/ApiListener: Finished reconnecting to endpoint 'main.em.lan' via host '192.168.53.210' and port '5665'
[2019-10-18 08:38:45 +0200] information/ApiListener: Requesting new certificate for this Icinga instance from endpoint 'main.em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Sending config updates for endpoint 'main.em.lan' in zone 'em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Finished sending config file updates for endpoint 'main.em.lan' in zone 'em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Syncing runtime objects to endpoint 'main.em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Finished syncing runtime objects to endpoint 'main.em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Finished sending runtime config updates for endpoint 'main.em.lan' in zone 'em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Sending replay log for endpoint 'main.em.lan' in zone 'em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Replayed 9 messages.
[2019-10-18 08:38:45 +0200] information/ApiListener: Finished sending replay log for endpoint 'main.em.lan' in zone 'em.lan'.
[2019-10-18 08:38:45 +0200] information/ApiListener: Finished syncing endpoint 'main.em.lan' in zone 'em.lan'.
The logs don’t provide any sorts of syncing the zone site1.em.lan as they should. Try enabling the debug log on both instances to gather more insights about the synced files.
I don’t see a bug yet, but I am really busy with other things right before OSMC.
One thought on this - the satellite logs still don’t tell anything about the satellite zone. Is that zone configured in zones.conf on the satellite?
Also, on a second look, the parent attribute is missing for object Zone "site1.em.lan" - so the master doesn’t know anything about this child zone and as such, no trust relationship is established and no config is synced.
I’ve moved the satellites from director to zones.conf close to the 2.11 update (and have missed to add parent). That’s why I thought this update might be the root cause (but was also thinking, no one else complains a similar issue - so there must be something wrong with my setup).