如何调试kube-proxy中的错误:对等重置连接 [英] How to debug error in kube-proxy: Connection reset by peer

问题描述

我的kube-proxy错误:

I got errors in my kube-proxy:

E0107 21:48:57.738867       1 proxysocket.go:160] I/O error: read tcp 10.2.11.253:37568: connection reset by peer

如何快速跟踪哪个吊舱具有IP 10.2.11.253?我怎么知道是哪个请求，从哪个吊舱到哪个吊舱?

How can I trace quickly which pod has IP 10.2.11.253? And how can I know which request that was, from which pod to which pod?

还是我们可以将kube-proxy日志级别更改为详细或调试?

Or can we change the kube-proxy log level to verbose or debug?

我遇到了另一个错误，与connection reset错误相同，但是IP是节点的IP

I got another errors, same connection reset error, but the IP is a node's IP

E0107 21:52:53.483363       1 proxysocket.go:160] I/O error: read tcp 192.168.166.180:11732: connection reset by peer

192.168.166.x是我的kubernetes节点子网，但是kube-proxy如何将请求转发到节点IP?

192.168.166.x is my kubernetes node subnet, but how can kube-proxy forwards request to a node IP?

我将kubelet 1.0.1和CoreOS v773.1.0(docker 1.7.1，内核4.1.5)用作群集节点.

I'm using kubelet 1.0.1 and CoreOS v773.1.0 (docker 1.7.1, kernel 4.1.5) as my cluster nodes.

感谢您的帮助！

推荐答案

在我的情况下，这是因为kube-proxy(v1.1.4)缺少--proxy-mode=iptables标志.显然，在1.1.4中，默认值是iptables以外的其他值，并且指定该标志会使日志立即停止喷出这些消息.

In my circumstance, it was because kube-proxy (v1.1.4) was missing the --proxy-mode=iptables flag. Evidently in 1.1.4, the default is something other than iptables, and specifying that flag made the logs immediately stop spewing those messages.

这篇关于如何调试kube-proxy中的错误:对等重置连接的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！