Upgrade whole system to r2.11.0-1, everything worked fine, except one host. I receive this notification:
Icinga 2 has been running for 5 hours, 18 minutes and 23 seconds. Version: r2.11.0-1; Last zone sync stage validation failed at 2019-09-23 08:02:42 +0200
Can’t find any hint, what to do. I receive notification for this machine, but how could i solve this failed sync?
I have had the same 'problem" and found out that you can find a startup.log in case there are startup problems. (no problems means no file;) (described as zone sync stage validation that failed)
In my case those came from a service change on the master zone but on that side you wont see it will gives errors on the endpoint/satellite.
Check the stage zone for errors and look for the startup.log file. ( icinga2 daemon -C )
/var/lib/icinga2/api/zones-stage
Dont know if it’s necessary but I reloaded the service on the endpoint/satellite and master.
i see the exact same behaviour. Except that it does not happens on every reload/config change but remains until i delete /var/lib/icinga2/api/zones and /var/lib/icinga2/api/zones-stage.
Config validations via “icinga2 daemon -C” and the debug log looks completly fine to me.
It occurs (almost) always on the same satellite in a HA zone.
Could you, just for testing sake, stop icinga on that agent, delete /var/lib/icinga2/api/zones and /var/lib/icinga2/api/zones-stage , start icinga service ?
Btw, you master should have at least the same version as you agent otherwise you’ll get such message to. If that’s not possible, downgrade your agent to match the master.
I already try to delete /var/lib/icinga2/ icinga2.statemodified-attributes.conf and /var/lib/icinga2/api/ packegeszoneszones-stages and restart the service.
[2020-02-07 07:53:29 +0100] information/ApiListener: Received configuration updates (2) from endpoint ‘98lipmoni1’ do not qualify for production, not triggering reload.
Hi all,
The Icinga2 version on the master is r2.14.0-1, and the version on the satellite is r2.11.2-1. I am experiencing a problem with my Icinga2 server; the configurations from the master won’t synchronize to the satellite anymore due to the error below. The system worked fine for a few months, but when I attempted to add another satellite to the system, I noticed that the configurations wouldn’t synchronize to the satellite.
Can you provide me with a hint on how to fix this error, please?
Note the hosts was run on the master use the same template and are fine!
Error.
[2023-11-10 16:51:29 -0600] critical/config: Error: Argument is not a callable object.
Location: in /var/lib/icinga2/api/zones-stage//wi-madison-imms/director/host_templates.conf: 1:6-1:45
/var/lib/icinga2/api/zones-stage//wi-madison-imms/director/host_templates.conf(1): if (! get_template(Host, “ga-camera-template”)) { template Host “ga-camera-template” {
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
/var/lib/icinga2/api/zones-stage//wi-madison-imms/director/host_templates.conf(2): import “camera_template”
/var/lib/icinga2/api/zones-stage//wi-madison-imms/director/host_templates.conf(3): import “dummy_template”
[2023-11-10 16:51:29 -0600] critical/cli: Config validation failed. Re-run with ‘icinga2 daemon -C’ after fixing the config.
root@imms2-ird-relay:/var/lib/icinga2# tail -f /var/log/icinga2/icinga2.log
[2023-11-10 16:51:28 -0600] information/ApiListener: Received configuration updates (11) from endpoint ‘imms2’ are different to production, triggering validation and reload.
[2023-11-10 16:51:29 -0600] critical/ApiListener: Config validation failed for staged cluster config sync in ‘/var/lib/icinga2/api/zones-stage/’. Aborting. Logs: ’