For some reason, I can’t provide more than 2 links in the post. In my opinion, it makes it more difficult to understand, but it is not up to me to decide. So below I use the following aliases:
I am trying to configure icinga2 to monitor a couple of machines. The icinga2-machine is behind a firewall of our organization, while the monitored machines are outside of it.
icinga2 daemon -C I get the following error:
... [2021-01-11 16:12:46 +0100] information/ApiListener: My API identity: wrong-link [2021-01-11 16:12:46 +0100] critical/config: Error: Endpoint object for 'wrong-link' is missing. Location: in /etc/icinga2/features-enabled/api.conf: 4:1-4:24 ...
The problem here is that the right DNS name of our icinga2-machine is ‘correct-link’. The DNS server of our organization only provides the ‘wrong-link’, which isn’t visible outside of our local network.
I am not entirely sure whether I understood everything correctly, but it appears to me that if I convince Icinga2 to use ‘correct-link’ as “My API identity”, the problem might be resolved. But I didn’t find a way to do that. I modified all the config files located in the /etc folder removing ‘xaas’ suffix from the DNS names. When I run
nslookup XXX.XXX.XXX.XX I get the correct DNS ‘correct-link’ . Not sure why icinga2 still gets the wrong one (with xaas).
I would be happy to provide more information if needed, but I am not even sure what else to provide.