3:11 p.m.
Hi Maciej,
hi all,
I get reproducible the following error on service/icinga_web
TASK [debops.icinga_web : Kickstart Icinga Director configuration]
***********************************************************************************************************************************************
fatal: [erdmaennchen.datenkollektiv.net]: FAILED! => {"changed": true,
"cmd": ["icingacli", "director", "kickstart",
"run"], "delta":
"0:00:00.260849", "end": "2019-05-23 14:46:38.305353",
"msg": "non-zero
return code", "rc": 1, "start": "2019-05-23
14:46:38.044504", "stderr":
"", "stderr_lines": [], "stdout": "ERROR:
Icinga\\Exception\\ConfigurationError in
/usr/local/src/icinga_web/github.com/Icinga/icingaweb2-module-director/library/Director/KickstartHelper.php:348
with message: I found no Endpoint object called \"erdmaennchen\" on
erdmaennchen:5665", "stdout_lines": ["ERROR:
Icinga\\Exception\\ConfigurationError in
/usr/local/src/icinga_web/github.com/Icinga/icingaweb2-module-director/library/Director/KickstartHelper.php:348
with message: I found no Endpoint object called \"erdmaennchen\" on
erdmaennchen:5665"]}
The same thing I got if I run icingacli director kickstart run from
command line. So probably it's not an icinga problem.
But maybe someone can point me to the right direction? I didn't found
anything usable in relation with this error message.
I did until now:
setup a new host with the roles
icinga
icinga_db
icinga_web
one after one.
icinga web is up and running. I can login, I see the localhost - but in
the Icinga-Directory I can't add any hosts. And Icinga doesn't know any
check commands.
On -> Icinga-Director -> Deployments -> create config I get the error:
Unable to detect your deployment endpoint. I was looking for the first
endpoint configured with an assigned API user in the "master" zone.
Migrating from nagios I was hoping not to have to go to deep into icinga...
I checkt already fqdn. It's all fine.
Kind regard
Jan
1:27 p.m.
On May 23, Jan Kowalsky wrote:
I get reproducible the following error on service/icinga_web
/usr/local/src/icinga_web/github.com/Icinga/icingaweb2-module-director/library/Director/KickstartHelper.php:348
with message: I found no Endpoint object called \"erdmaennchen\" on
erdmaennchen:5665", "stdout_lines": ["ERROR:
I checkt already fqdn. It's all fine.
Is it? What is 'erdmaennchen', the host on which you are deploying Icinga
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:
openssl x509 -in /etc/pki/realms/domain/default.crt -text
Let me know what you found out. If nothing helped, we could arrange a session
via remote desktop setup so that I could look around.
Good luck,
Maciej
1:43 p.m.
Hi Maciej,
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
>
>
/usr/local/src/icinga_web/github.com/Icinga/icingaweb2-module-director/library/Director/KickstartHelper.php:348
> 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
deploying Icinga
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 ;-)
Best regards
Jan
2034
days inactive
2039
days old
2 comments
2 participants
participants (2)
-
Jan Kowalsky -
Maciej Delmanowski