Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #12808] Endpoint not created #4692
This issue has been migrated from Redmine: https://dev.icinga.com/issues/12808
Created by jsmartel68 on 2016-09-27 10:09:58 +00:00
This issue is the same as the rejected issue #10688. We have just upgraded to 2.5.4 and still have the problem where we try to add a node but the icinga server does not seem to create it properly. But we have a similarly named server in our staging environment that does work.
To add the node we use "icinga2 node wizard".
When the node tries to connect to the master we see the following.
The node seems to be at least partially created on the master.
But nothing shows up in the repository.d/endpoints for this node.
I have followed the suggestions in http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/troubleshooting and confirmed the SSL stuff is correct.
Could you suggest some more troubleshooting steps or perhaps a way to create the node on the server side?
Thank you in advance,
Parent Task: #13257
Updated by mfriedrich on 2016-09-27 11:08:22 +00:00
Did you run "node list" and "node update-config" prior to checking the repository.d/endpoints directory?
Can you show the output of
Updated by jsmartel68 on 2016-09-27 12:16:29 +00:00
Yes, I did run "node update-config" but could not see the client. It does, however, show up in "node list".
I have attached as text files the output of the two ls commands you requested.
Updated by jsmartel68 on 2016-09-27 12:33:15 +00:00
I forgot to also mention the pattern in the problem hosts that we have seen. We first create a host in our staging environment with name stage-client-1.srv.company.com. Then after testing, we create a host in our production environment without stage at the front, such as client-1.srv.company.com. While it seems unlikely that this would be causing the problem, I did want to point it out. Here are two examples where the stage server works fine in Icinga but the non-stage has the same error as described:
Updated by mfriedrich on 2016-11-07 15:41:02 +00:00
I do see that endpoint config file 'stage-gap-batch-ingestion-1.srv.company.com.conf' in your etc/repository.d directory. So node update-config is working fine and creating things. Probably your Icinga 2 node isn't aware of the configuration changes and was not restarted properly.
I'd recommend using the "top down" approach though where you'll either distributed the config from the master to the clients entirely, or at least use them as command endpoints.
Updated by jsmartel68 on 2016-11-08 08:18:22 +00:00
Hi, thanks for the reply. However, it is not the stage server that is the problem. The problem is the server without the "stage-" in the front. If you look in the repository.d directory there should be two hosts: stage-gap-batch-ingestion-1.srv.company.com.conf and gap-batch-ingestion-1.srv.company.com.conf, but there is only the one.
Updated by mfriedrich on 2016-12-07 21:35:54 +00:00
No idea about that sorry. But as you asked, adding this directly on the node itself instead of using node update-config, I'd suggest to migrate to top down while at it. Additional docs have been added for 2.6 too - https://docs.icinga.com/icinga2/snapshot/doc/module/icinga2/toc\#!/icinga2/snapshot/doc/module/icinga2/chapter/distributed-monitoring#distributed-monitoring-bottom-up-migration-top-down