Can't change zone/endpoint for hosts

Hi,

  • icinga2 : 2.14.2-1+debian11
  • icingadb : 1.2.0-1+debian11

I’m having some trouble, I have a master and 3 satellites (3 zones so 1 satellite per zone).
Everything is working alright, zones/endpoints are set on the hosts through the synchronization from the sources.
But I can’t seem to change the zone for hosts afterwards. According to the director, the configuration is saved, but when I look at Check Statistics, the source is the old endpoint.
Also the checks for the host tend to be overdued; If I check the logs :

[2024-07-17 10:00:50 +0200] notice/ClusterEvents: Discarding ‘check result’ message for checkable ‘HOST!SNMP_Memory’ from ‘OLD_ENDPOINT’: Unauthorized access.

That seems to confirm that the old endpoint is sending the check results but the master knows it’s not supposed to be him. If I check the logs on the old endpoint, I do see the checks being done; On the new endpoint, nothing.

Again, old and new endpoint are properly working for plenty of hosts; but changes don’t seem to work after sync.

Am I missing something ?

did you also adapt the config on the agent/satellites?

I’m confused, isn’t the master supposed to “send” the config to his satellites ?

yes but not the config that is not written by the master, which is the initial config you created using

icinga2 node wizard

I didn’t really get what you said but kept looking in logs;
Turns out I got plenty of those on my satellites :

[2024-07-17 15:53:58 +0200] critical/config: Error: Validation failed for object ‘HOST_ZONE_A!parent_down’ of type ‘Dependency’; Attribute ‘parent_host_name’: Object ‘HOST_ZONE_B’ of type ‘Host’ does not exist.

OK so the satellite in the Zone A doesn’t know HOST_ZONE_B because it’s not in the same zone; If I move it to zone A, no problem then and changing endpoints do work.

So what’s my move then ?
Should I just have one zone and have my different endpoints in it ?

Hello, :wave:

As per my knowledge, ensure that the zone configuration and endpoint mappings are correctly updated across your master and satellites. Double-check permissions and access settings to resolve the “Unauthorized access” error, and verify that changes made through the director are effectively applied and propagated.

I hope this will help you.
Respected community member :smiling_face_with_three_hearts:

Please share configs from a working host and a non-working one.
That should help figuring out where the problem lies.