consul icon indicating copy to clipboard operation
consul copied to clipboard

Consul connection error on port 8300

Open HalacliSeda opened this issue 3 years ago • 0 comments

Hello,

I use Consul 1.13.1 I have two server (as an example): 10.10.10.1, 10.10.10.2 I set up consul server on both. consul.json are same on both: { "bind_addr": "10.10.10.1", "client_addr": "0.0.0.0", "datacenter": "datacenter-01", "bootstrap_expect": 3, "data_dir": "/var/lib/consul", "encrypt": "", "disable_update_check": true, "server": true, "ui": true, "rejoin_after_leave": true, "retry_join": ["10.10.10.1","10.10.10.2","......."], "acl": { "enabled": true, "default_policy": "deny", "tokens": { "agent": "" } } } { "bind_addr": "10.10.10.2", "client_addr": "0.0.0.0", "datacenter": "datacenter-01", "bootstrap_expect": 3, "data_dir": "/var/lib/consul", "encrypt": "", "disable_update_check": true, "server": true, "ui": true, "rejoin_after_leave": true, "retry_join": ["10.10.10.1","10.10.10.2","......."], "acl": { "enabled": true, "default_policy": "deny", "tokens": { "agent": "" } } }

consul members output like that: Node Address Status Type Build Protocol DC Partition Segment ha1 10.10.10.1:8301 alive server 1.13.1 2 datacenter-01 default ha2 10.10.10.2:8301 alive server 1.13.1 2 datacenter-01 default

But I got an error both server like that: [WARN] agent: [core]grpc: addrConn.createTransport failed to connect to {ha1:8300 ha1.compute.internal 0 }. Err: connection error: desc = "transport: Error while dialing dial tcp 10.10.10.2:0->10.10.10.1:8300: operation was canceled". Reconnecting...

Port 8300 used for consul service on both server. I check ports with telnet and there is no problem: telnet 10.10.10.1 8300 Trying 10.10.10.1... Connected to 10.10.10.1. Escape character is '^]'.

I did not get an error in Consul 1.12.1. Is this a bug in Consul 1.13.1 ?

Thanks, Seda

HalacliSeda avatar Sep 02 '22 10:09 HalacliSeda