【问题标题】:RuntimeError: SSH to the cluster failed to start when using telepresenceRuntimeError: 使用网真时 SSH 到集群启动失败
【发布时间】:2020-02-21 09:35:21
【问题描述】:

当我使用网真调试远程kubernetes时,抛出这个错误:

RuntimeError: SSH to the cluster failed to start

这是详细输出:

~ ⌚ 17:26:43
$ telepresence
T: How Telepresence uses sudo: https://www.telepresence.io/reference/install#dependencies
T: Invoking sudo. Please enter your sudo password.
Password:
T: Starting proxy with method 'vpn-tcp', which has the following limitations: All processes are affected, only one telepresence can run
T: per machine, and you can't use other VPNs. You may need to add cloud hosts and headless services with --also-proxy. For a full list
T: of method limitations see https://telepresence.io/reference/methods.html
T: Volumes are rooted at $TELEPRESENCE_ROOT. See https://telepresence.io/howto/volumes.html for details.
T: Starting network proxy to cluster using new Deployment telepresence-1582277212-643104-29913

Looks like there's a bug in our code. Sorry about that!

Traceback (most recent call last):
  File "/usr/local/bin/telepresence/telepresence/cli.py", line 135, in crash_reporting
    yield
  File "/usr/local/bin/telepresence/telepresence/main.py", line 68, in main
    socks_port, ssh = do_connect(runner, remote_info)
  File "/usr/local/bin/telepresence/telepresence/connect/connect.py", line 119, in do_connect
    args.from_pod
  File "/usr/local/bin/telepresence/telepresence/connect/connect.py", line 70, in connect
    raise RuntimeError("SSH to the cluster failed to start. See logfile.")
RuntimeError: SSH to the cluster failed to start. See logfile.


Here are the last few lines of the logfile (see /Users/dolphin/telepresence.log for the complete logs):

  50.2  37 | QoS Class:       Burstable
  50.2  37 | Node-Selectors:  <none>
  50.2  37 | Tolerations:     node.kubernetes.io/not-ready:NoExecute for 360s
  50.2  37 |                  node.kubernetes.io/unreachable:NoExecute for 360s
  50.2  37 | Events:
  50.2  37 |   Type    Reason     Age   From                    Message
  50.2  37 |   ----    ------     ----  ----                    -------
  50.2  37 |   Normal  Scheduled  38s   default-scheduler       Successfully assigned dabai-fat/telepresence-1582277212-643104-29913-7bb5765b6-7xflh to azshara-k8s01
  50.2  37 |   Normal  Pulled     35s   kubelet, azshara-k8s01  Container image "datawire/telepresence-k8s:0.104" already present on machine
  50.2  37 |   Normal  Created    34s   kubelet, azshara-k8s01  Created container telepresence-1582277212-643104-29913
  50.2  37 |   Normal  Started    34s   kubelet, azshara-k8s01  Started container telepresence-1582277212-643104-29913
  50.2 TEL | [37] ran in 0.50 secs.

我应该怎么做才能解决这个问题?我的kubernetes服务器版本是1.15.2。客户端版本:1.17.3。

【问题讨论】:

  • 正如它告诉你的那样,查看日志以获取更多信息。

标签: kubernetes telepresence


【解决方案1】:

在你的远程 kuberentes 集群主机上安装 socat,我用的是 CentOS,所以像这样安装:

sudo yum install socat -y

如果使用 ubuntu/debian,安装如下:

sudo apt-get install socat -y

【讨论】:

    猜你喜欢
    • 2016-07-03
    • 2011-04-04
    • 2015-01-23
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2015-10-12
    • 2018-09-04
    相关资源
    最近更新 更多