Hii, this indicates that your two hosts are depending on each other. Meaning, your host TE-Kamera-WS.linz.liferadio.at depends on TE-Kamera-WS.linz.test.at, which in turn depends on TE-Kamera-WS.linz.liferadio.at. This is a dependency cycle.
Thanks, can you please tell me how I can find out where this dependency is set? I´ve already checked the /var/lib/icinga2/director folders but I can´t see this kind of dependency. I am using the director. Should I simply delete this entry? What is the best way to fix it?
This host is not affected by this problem since it doesn’t define host-vm in its groups attribute.
Assuming this is the only dependency you have, then you either need to remove the host-vm group from one of the two hosts, or manually define the parent_host_name attribute in the dependency apply rule. You may also change your assign where condition to something else that matches only either host.
Yes, I´ve deleted host-vm, but how do I reload the director when the process is broken? The host had defined host-vm prior. I can´t deploy any changes till now because the process is broken.
I´ve commented out the depedency and host group and deleted it from the host, but the errors persists.
I´ve edited the files - how can I start icinga2 manually? Also the dpkg upgrade didn´t run fully because it can´t write the configurations of the packages. It seems that the manual config file changes of the director are not recognized anyhow.
Thanks, no the validition failes although I´ve edited the director configs manually and also I can´t start via systemd. I´ve tried to remove and reinstall icinga which also fails. Could this files be stored at another location then /var/lib/icinga2/api/zones/TE-Icinga-VM.linz.xy.at/director/hosts.conf?
Thanks, with grep I found two deployment folders, where this configs where stored: /var/lib/icinga2/api/packages/director/0f10e8cf-48df-44b0-8455-9a98967b138c/zones.d now the upgrade worked and Icinga2 is running again