Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #10216] Clarify on cluster/client naming convention and add troubleshooting section #3436
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10216
Created by ziaunys on 2015-09-24 21:40:00 +00:00
I have a situation where I have a client and master separated by a firewall. I have to NAT connections established by the client to reach the master node. I can verify the connection from both the master -> client and client-> master. However, checks executed by the client are stuck in a pending state. The master's "cluster-zone" check for the client is succesful. When I enable debug logging on the client, I can see the check results are being relayed to the master correctly, but the state is never updated.
The problem seems to be that it won't relay checks back to the parent node correctly because the A record pointing at the static NAT address is different than the one pointing at the internal address. It seems like external nodes shouldn't be dependent on DNS.
I don't actually see an error message indicating any issue, but one theory I've had is maybe it was failing because the external hostname didn't match the hostname set on the Puppet cert as an alt name. In this situation I guess it wouldn't really be a bug.
2015-09-25 09:34:01 +00:00 by mfriedrich 6555e42
2015-09-25 09:36:46 +00:00 by mfriedrich 4c87f62
Updated by mfriedrich on 2015-09-24 21:51:46 +00:00
Is applied all the way through?
Updated by ziaunys on 2015-09-24 22:11:31 +00:00
Ahh.. that's the issue. The endpoint names didn't match because the external hostname doesn't match the CN which was more of a configuration issue on my part. Thanks for pointing that out.
Updated by mfriedrich on 2015-09-25 07:43:38 +00:00
I'll change that into a documentation issue, and add that information to the remote clients chapter.
Updated by mfriedrich on 2015-09-25 09:30:59 +00:00
Also managed to add a dedicated troubleshooting chapter.