thanks for answer which put me in the right direction.
Am 24.05.19 um 13:27 schrieb Maciej Delmanowski:
On May 23, Jan Kowalsky wrote:
> I get reproducible the following error on service/icinga_web
> with message: I found no Endpoint object called \"erdmaennchen\" on
> erdmaennchen:5665", "stdout_lines": ["ERROR:
> I checkt already fqdn. It's all fine.
I did. But I didn't bootstrap the host again after fixing hostname etc.
So it was wrong in ansible facts.
Is it? What is 'erdmaennchen', the host on which you are
Director? I would think that it would be a fully qualified domain name, with
some kind of domain. It's important, because Icinga uses TLS to communicate
with the clients, which means X.509 certificates, which means FQDNs used as
common names. The 'debops.icinga*' set of roles is geared towards usage with
'debops.pki', which means that a working DNS setup is required.
So, I would look at DNS, both on the Ansible Controller and on the remote
host. Do both hosts see the same results when you query the hostname and FQDN
of that host? What do you get when you run 'hostname --fqdn' or
'dnsdomainname' on the remote host?
You should then check if the generated X.509 certificates used for Icinga have
the correct common names, most likely with wildcard domain. You can do this
with the command:
Ideed, the certificate is generated only for fqdn. But this is ok.
And now it works so far.
Next problems are coming soon ;-)