For complex issues please use https://discuss.hashicorp.com/c/consul/, https://github.com/hashicorp/consul/issues or https://groups.google.com/forum/#!forum/consul-tool.
Interested in hearing your thoughts
https://discuss.hashicorp.com/t/how-to-use-prepared-query-in-retry-join/26943
Outside using the way a prepared query can be accessed over DNS, is there a more direct way of putting in an expression in retry_join such that it uses prepared query in the same style of the way "provider" expressions work in retry_join?
I want to try using a prepared query to self discover consul peers in retry_join (assuming the consul server resolving the prepared query knows about said peers)?
4 replies
Hi all, we had Consul Connect working with Vault as an external CA for a few weeks up until over the weekend, on Saturday our proxies have stopped working, displaying 'Connection Refused' after the initial request. We can't get the minimal Nomad Consul Connect "countdash" example working, which was fine previously. We haven't had any configuration changes, the Vault CA periodic token is still valid and it seems like certs are still being generated and assigned to new proxies. We also can't find anything immediately obvious in metrics or logs, wondering if anyone has experienced something similar? We are on Consul 1.9.6, Nomad 1.0.1 and Envoy 1.16.4
2 replies
Iāve just rebuilt my consul test cluster, basic 3 quorum set nodes with around ~20 members - one of the members is a synlogy NAS box with consul 1.10.1 container running as a cluster member, (itās an interesting member to have) the 3 consul raft servers are all showing an error from the IP address of the NAS box running the consul member container
Jul 21 10:05:35 jake consul[7781]: 2021-07-21T10:05:35.282Z [ERROR] agent.server.rpc: unrecognized RPC byte: byte=71 conn=from=10.11.216.64:52022
Jul 21 10:07:12 nog consul[5613]: 2021-07-21T10:07:12.173Z [ERROR] agent.server.rpc: unrecognized RPC byte: byte=71 conn=from=10.11.216.64:41866
(from two different nodes - jake and nog)
Iāve stopped the consul container on the NAS box, and the errors persist
I canāt get a clear view on my head on whatās happening here, the logs show me that the connection is coming from 10.11.216.64 (the NAS box) - how is this happening with the consul agent not running
secondly, I donāt understand what the RPC error actually is, as an RPC error this generic could mean many things
just for completion the cluster leader is also getting the same error
Jul 21 10:10:53 wesley consul[15814]: 2021-07-21T10:10:53.570Z [ERROR] agent.server.rpc: unrecognized RPC byte: byte=71 conn=from=10.11.216.64:52784
itās prometheus running on the same node, querying the consul servers on the wrong port, consul is expecting RPC and prometheus is scraping with a standard TCP request, hence why itās unrecognised RPC
Hi all, we've been testing out
consul connect ca set-config to rotate between Vault CA endpoints gracefully. The issue is that while existing proxies work fine during the rotation process, new proxies can't seem to reference the new CA bundle until the Consul leader is restarted and an election is forced. Restarting the leader immediately after setting the config causes old proxies to break for a few minutes, however, so this isn't an option. Has anyone dealt with this before? We are on Consul 1.9.6, Envoy 1.16.4.
Hi all, after upgrading a linux server from U16 to U18 (without touching consul) I'm having the error: Node name XXX is reserved by node YYY. I have tried a number of things (leave, force-leave, use the API to deregister and then register with the new ID..) without result. There is anyway to set the new ID in the cluster? Anything else? We are using consul 1.8.4 Thanks !
(did you not want to move to Ubuntu 20.04 ?
We cannot upgrade to Ubuntu 20 :(
Stopping consul and editing node-id with the old value will solve the problem?
Thanks a lot @ikonia although IĀ“m not sure if this was the correct way to fix the issue
but that file seems to cause lots of problem if the instance changes in some way / replaced with the same hostname
hi all, so we are running consul in heavy scale (around 12K nodes in a cluster). We see something very wired. We have nodes that exists in the nodes catalog but not in the consul members (serf). This is reflected also in the consul UI as those nodes appear not to have serf health check but they do appear in the ui. of course consul agent is running on those hosts and from the agent perspective all is fine, although it is not listed in the members of the cluster. Any help will be great, we are breaking our heads against the wall with this fo long time
Thanks for your replays.
@pierresouchay , our cluster is not that loaded from CPU or Memory perspective.Also calling the catalog deregister is problematic as those nodes are actually running and they think they are part of the cluster. The only valid solution we have found was restarting the node itself, but at our scale checking this is it not trivial. It feels like something is broken when syncing the serf members and catalog if we end up in such cases. @gc-ss Attaching CPU load on the server hosts
@pierresouchay , our cluster is not that loaded from CPU or Memory perspective.Also calling the catalog deregister is problematic as those nodes are actually running and they think they are part of the cluster. The only valid solution we have found was restarting the node itself, but at our scale checking this is it not trivial. It feels like something is broken when syncing the serf members and catalog if we end up in such cases. @gc-ss Attaching CPU load on the server hosts
Deregister the node would not be an issue, the node would register again when anti-entropy would trigger (i would say around 10/15 minutes on such a big cluster). If it doez not, it means something is broken on the node itself, so restarting the node looks like the only valid option. Nothing weird on those nodes logs?
Hey folks - does anyone know how the hexidecimal value at the beginning of the service name that's returned from a dig SRV is generated? Is there anyway to know this value from a service running in consul (via env var, or some deterministic method). For example when you dig for an SRV record, you're given a dns name like ac1f8802.addr.dc1.consul. Where does that ac1f8802 come from, and is it possible to know that from within a service running in consul?
172.31.136.2
Like if I'm a service and want to know that hostname, it looks like I can derive it from <hex_value>.addr.<dc>.<tld>. Is there an easy way to go from IP address -> hex value?
Thank you sir
š