New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #10688] Endpoint not created #3688
Comments
Updated by jflach on 2015-11-20 10:33:11 +00:00
Lists all your endpoints and the files they come from. |
Updated by bert2002 on 2015-11-20 11:27:44 +00:00 Hi, the endpoint for the hosts is not created.
Running update-config, etc. does not help either. :( |
Updated by jflach on 2015-11-20 11:43:53 +00:00 Disregard my earlier version of the comment, please Run icinga2 object list --type Endpoint --name app-stats-1.srv.company.com Don't grep, you need the whole output |
Updated by bert2002 on 2015-11-20 12:45:50 +00:00 Hi, same issue. no output, only for the staging servers. |
Updated by gbeutner on 2015-11-21 03:37:40 +00:00 FWIW I'm unable to reproduce this on a new installation. |
Updated by mfriedrich on 2015-11-25 14:16:34 +00:00
Please re-test this issue with the latest 2.4.0 release. |
Updated by bert2002 on 2015-12-01 14:26:00 +00:00 dnsmichi wrote:
okay I updated to 2.4.0 (centos) but problem still exist. |
Updated by bert2002 on 2015-12-08 08:51:28 +00:00 When a, not working, client connects. I get following error:
I double checked the certificates and they are identical. Installed openssl versions: icinga server:
client:
Other clients (with a different name schema) are working with the same openssl version. |
Updated by bert2002 on 2015-12-08 10:17:00 +00:00 Okay something "funny" happened. We configured some custom checks on the client and they are getting created on the icinga server. Of course its not working, because the zone for the host does not really exist. I would have expected that the custom checks get ignored as all other checks.
|
Updated by mfriedrich on 2016-02-24 21:55:28 +00:00
I can't follow here. How are these config objects created on the master? Is the client node's zone configured with the master zone being its parent? |
Updated by mfriedrich on 2016-03-18 16:11:17 +00:00
Since we cannot reproduce the issue here and it is not obvious which cli command causes the error, I'll close the issue. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10688
Created by bert2002 on 2015-11-20 10:00:36 +00:00
Assignee: (none)
Status: Rejected (closed on 2016-03-18 16:11:17 +00:00)
Target Version: (none)
Last Update: 2016-03-18 16:11:17 +00:00 (in Redmine)
Hi,
we have Icinga 2.3.10 running and get clients use the api to connect and push results. We just created a new environment from a staging environment and no client in the new environment gets any endpoint/zone/hosts on the icinga server.
The only difference between the two environments are the names:
stage: stage-app-stats-1.srv.company.com
prod: app-stats-1.srv.company.com
The staging clients have no problem and everyone is happy. The production clients cant connect and get refused from the icinga server with this error (debuglog):
Apparently this is a problem with the certificates, but according to the troubleshooting guide they are okay:
When I try to create a new endpoint with the name of the production environment i get told that the endpoint already exist:
But I cant find it in any way on the system (status file, etc.).
I dont understand the problem, or what I am missing (we have an automated deployment for the client and its working for other name schemas/new server without any problem). Any idea where/what I could check? May be dump some data from Icinga, database, etc.?
Any help appreciated.
bert2002
The text was updated successfully, but these errors were encountered: