Skip to content
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

etcd: failed to receive watch request from grpc stream(rpc error:code =Canceled desc = context canceled) #5

Open
BiaoLiu opened this issue Jun 15, 2018 · 10 comments

Comments

@BiaoLiu
Copy link

BiaoLiu commented Jun 15, 2018

按照你的步骤一步步来实现,查看calico节点运行情况的时候,找不到节点

Calico process is running.

IPv4 BGP status
No IPv4 peers found.

IPv6 BGP status
No IPv6 peers found.

再查看etcd运行情况,发现报了错误:

failed to receive watch request from gRPC stream ("rpc error: code = Canceled desc = context canceled")
@liuyi01
Copy link
Owner

liuyi01 commented Jun 15, 2018

ip问题的概率较大,是否有外网ip?网卡是否正确?

@BiaoLiu
Copy link
Author

BiaoLiu commented Jun 15, 2018

网卡没有问题,虚拟机部署的

@racooncry
Copy link

我也是这个问题,请问一下是为什么

@racooncry
Copy link

@BiaoLiu 请问一下你解决这个问题了吗 ?

@BiaoLiu
Copy link
Author

BiaoLiu commented Aug 20, 2018

@racooncry 我后面是使用kubeadm部署了

@dengqiangloveju
Copy link

没得解决方案啊?

@kecode
Copy link

kecode commented Jan 8, 2019

按照你的步骤一步步来实现,查看calico节点运行情况的时候,找不到节点

Calico process is running.

IPv4 BGP status
No IPv4 peers found.

IPv6 BGP status
No IPv6 peers found.

再查看etcd运行情况,发现报了错误:

failed to receive watch request from gRPC stream ("rpc error: code = Canceled desc = context canceled")

你仔细看下日志,应该是之前的simple版的服务没有删除干净,我这边也是你这样的,删除干净就好了。

@Michaelsongyang
Copy link

按照你的步骤一步步来实现,查看calico节点运行情况的时候,找不到节点

Calico process is running.

IPv4 BGP status
No IPv4 peers found.

IPv6 BGP status
No IPv6 peers found.

再查看etcd运行情况,发现报了错误:

failed to receive watch request from gRPC stream ("rpc error: code = Canceled desc = context canceled")

你仔细看下日志,应该是之前的simple版的服务没有删除干净,我这边也是你这样的,删除干净就好了。

我是一个全新的虚拟机,按照老师的步骤一步一步的实现,也是同样的错误

@kerwincsc
Copy link

我也遇到了此问题.
我在查看 work node 上的 calico 的日志时, 发现其显示不能连接到 etcd;
搜索后发现, 可能是 etcd 挂了. 回到 master node 上发现, etcd 正在运行, 但是其日志有报错, 即如上所述.
参考大家的描述, 尝试将 nat 网卡禁用, 改成桥接网卡, 问题依旧.
后来发现是我 master node 的防火墙未关, 关闭后, 两个 work node 可以正常连接到 master, master 上的 etcd 也不报错了. 使用 calicoctl node status, 发现两个节点正常连接上了.

@congmingdexiong
Copy link

请教各位,老师演示用虚拟机,ip就是固定一个,现在我使用阿里云服务器分公网和私网ip, 下面etcd配置, --listen-client-urls=http://172.26.178.195:2379, 必须写的是我私网IP,不然起不来;但是这样写的话,node节点kube-calico连过来会有错误 Dec 17 11:58:56 a docker[27052]: bird: Mesh_172_26_178_195: Socket error: bind: Address not available,求教大家怎么解!

Type=notify
WorkingDirectory=/var/lib/etcd/
ExecStart=/root/kubernetes/bin/etcd
--name=172.26.178.195
--listen-client-urls=http://172.26.178.195:2379,http://127.0.0.1:2379
--advertise-client-urls=http://172.26.178.195:2379
--data-dir=/var/lib/etcd
Restart=on-failure
RestartSec=5
LimitNOFILE=65536

master:

[root@iz8vbe8g1tunlrid957q2dz bin]# ./calicoctl node status
Calico process is running.

IPv4 BGP status
+----------------+-------------------+-------+----------+---------+
| PEER ADDRESS | PEER TYPE | STATE | SINCE | INFO |
+----------------+-------------------+-------+----------+---------+
| 47.105.223.158 | node-to-node mesh | start | 02:49:30 | Connect |
| 47.105.189.58 | node-to-node mesh | start | 02:49:30 | Connect |
+----------------+-------------------+-------+----------+---------+

node:
Calico process is running.

IPv4 BGP status
+----------------+-------------------+-------+----------+--------------------------------+
| PEER ADDRESS | PEER TYPE | STATE | SINCE | INFO |
+----------------+-------------------+-------+----------+--------------------------------+
| 47.105.189.58 | node-to-node mesh | start | 03:54:15 | Active Socket: Connection |
| | | | | closed |
| 172.26.178.195 | node-to-node mesh | start | 03:54:15 | Active Socket: Connection |
| | | | | closed |
+----------------+-------------------+-------+----------+--------------------------------+

IPv6 BGP status
No IPv6 peers found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants