Skip to content

Commit 2e4f0b5

Browse files
committed
[zh-cn]sync debug-service.md
Signed-off-by: xin.li <[email protected]>
1 parent 83469fc commit 2e4f0b5

File tree

1 file changed

+0
-12
lines changed

1 file changed

+0
-12
lines changed

content/zh-cn/docs/tasks/debug/debug-application/debug-service.md

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -811,21 +811,9 @@ I1027 22:14:54.040223 5063 proxier.go:294] Adding new service "kube-system/ku
811811
<!--
812812
If you see error messages about not being able to contact the master, you
813813
should double-check your Node configuration and installation steps.
814-
815-
One of the possible reasons that `kube-proxy` cannot run correctly is that the
816-
required `conntrack` binary cannot be found. This may happen on some Linux
817-
systems, depending on how you are installing the cluster, for example, you are
818-
installing Kubernetes from scratch. If this is the case, you need to manually
819-
install the `conntrack` package (e.g. `sudo apt install conntrack` on Ubuntu)
820-
and then retry.
821814
-->
822815
如果你看到有关无法连接主节点的错误消息,则应再次检查节点配置和安装步骤。
823816

824-
`kube-proxy` 无法正确运行的可能原因之一是找不到所需的 `conntrack` 二进制文件。
825-
在一些 Linux 系统上,这也是可能发生的,这取决于你如何安装集群,
826-
例如,你是手动开始一步步安装 Kubernetes。如果是这样的话,你需要手动安装
827-
`conntrack` 包(例如,在 Ubuntu 上使用 `sudo apt install conntrack`),然后重试。
828-
829817
<!--
830818
Kube-proxy can run in one of a few modes. In the log listed above, the
831819
line `Using iptables Proxier` indicates that kube-proxy is running in

0 commit comments

Comments
 (0)