etcd start without error, but can't accept connection #2868
Comments
|
@silenceleaf As you saw in the log, etcd is not started yet. It is still waiting for other. You have to start the other 4 peers. |
|
Question is even if I start other 4 peers, nothing happened in #1 machine. I can only config static mode of etcd. |
|
Network is fine. I can ping other machine without any issue. |
|
@silenceleaf You need to give all 5 members the same discovery token. It would be helpful if you can provide the configuration and log from all your 5 members. |
|
Two of my cloud config. These two machine can not find each other. coreos1 #cloud-config
hostname: coreos1
coreos:
etcd2:
name: coreos1
discovery: https://discovery.etcd.io/a0fc6f91ae40f46c1d3a6c1b4f4f34d8
initial-cluster-token: etcd2-cluster-1
initial-advertise-peer-urls: http://192.168.0.111:2380
listen-peer-urls: http://192.168.0.111:2380
# initial-cluster: coreos1=http://192.168.0.111:2380,coreos2=http://192.168.0.112:2380,coreos3=http://192.168.0.113:2380,coreos4=http://192.168.0.114:2380,coreos5=http://192.168.0.115:2380
advertise-client-urls: http://192.168.0.111:2379
listen-client-urls: http://192.168.0.111:2379
data-dir: /home/core/etcd2/
initial-cluster-state: new
# fleet:
# public-ip: 192.168.0.111
# etcd_servers: http://192.168.0.111:2379
# metadata: HomeCluster
units:
- name: 10-ens3.network
content: |
[Match]
MACAddress=52:54:00:fe:b3:c1
[Network]
Address=192.168.0.111/24
Gateway=192.168.0.1
DNS=8.8.8.8
- name: etcd2.service
command: start
# - name: fleet.service
# command: startcoreos2 #cloud-config
hostname: coreos2
coreos:
etcd2:
name: coreos2
discovery: https://discovery.etcd.io/a0fc6f91ae40f46c1d3a6c1b4f4f34d8
initial-cluster-token: etcd2-cluster-1
initial-advertise-peer-urls: http://192.168.0.112:2380
listen-peer-urls: http://192.168.0.112:2380
# initial-cluster: coreos1=http://192.168.0.111:2380,coreos2=http://192.168.0.112:2380,coreos3=http://192.168.0.113:2380,coreos4=http://192.168.0.114:2380,coreos5=http://192.168.0.115:2380
advertise-client-urls: http://192.168.0.112:2379
listen-client-urls: http://192.168.0.112:2379
data-dir: /home/core/etcd2/
initial-cluster-state: new
fleet:
public-ip: 192.168.0.112
units:
- name: 10-ens3.network
content: |
[Match]
MACAddress=52:54:00:fe:b3:c2
[Network]
Address=192.168.0.112/24
Gateway=192.168.0.1
DNS=8.8.8.8
- name: etcd2.service
command: start
# - name: fleet.service
# command: start |
|
The log of every machine said they are waiting for connection, but no connection come in. |
|
@silenceleaf That is great. The two you gave me work well. You just need to add 3 more. |
|
If you do not add 3 more, it will simply wait forever. |
|
@xiang90 Suppose even if I have only two machines, it should try to connect with each other. So, let me start more machine and have try. |
|
This the log of the third machine. Seems it find other peers from discovery service. But why no one try to connect other peers? |
|
I think you need to read the doc here https://github.com/coreos/etcd/blob/master/Documentation/clustering.md#etcd-discovery. As I said before, etcd will not start unless all your members are ready when you are using discovery service. I do not know why you think they should start to connect to each other. I can tell you they WILL NOT. |
|
@silenceleaf Go ahead to start the other 2 memebers. It will work. |
|
Aha, That is what I am confusing. Try it now, thanks for your quick response. |
etcd2 version: 2.01
I am using public discovery service
My configuration:
Journal is OK
journalctl -b -u etcd2 --no-pager
When I use:
It give me
When I check netstat -l
Recv-Q have one waiting request. I think it means network is ok. The data haven't been consumed by etcd2.
Because I can't use etcdctl, I don't know if etcd work well.
Would you mind diagnose this for me?
The text was updated successfully, but these errors were encountered: