tidb4.0.11 reload配置时报错：ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

🪐 TiDB 技术问题
1

为提高效率，请提供以下信息，问题描述清晰能够更快得到解决：
【 TiDB 使用环境】生产环境
【概述】使用tiup修改tidb集群配置时出现错误，执行命令：tiup cluster reload tidb-prod -R tidb
【背景】中控机和操作系统版本：CentOS Linux release 7.8.2003 (Core)；openssh版本：OpenSSH_8.8p1, OpenSSL 1.1.1l 24 Aug 2021
【现象】我做了如下验证，在中控机上使用ssh -v tidb@xxxx或 ssh -v tidb@xxx -i /home/tidb/.tiup/storage/cluster/clusters/tidb-prod/ssh/id_rsa均能正常访问集群内其他节点；在中控机上使用scp /home/tidb/.tiup/storage/cluster/clusters/tidb-prod/config-cache/pd-172.20.46.41-2379.service tidb@172.20.46.41:/tmp/pd_a37c8bcb-8d5e-4909-a282-6df293da4529.service或scp -i /home/tidb/.tiup/storage/cluster/clusters/tidb-prod/ssh/id_rsa /home/tidb/.tiup/storage/cluster/clusters/tidb-prod/config-cache/pd-172.20.46.41-2379.service tidb@172.20.46.41:/tmp/pd_a37c8bcb-8d5e-4909-a282-6df293da4529.service命令能正常拷贝
【业务影响】修改数据库配置后无法使之生效
【TiDB 版本】4.0.11
【附件】
[tidb@tidb-proxy01 ~]$ tiup cluster reload tidb-prod -R tidb
Starting component cluster: /home/tidb/.tiup/components/cluster/v1.8.1/tiup-cluster reload tidb-prod -R tidb
Will reload the cluster tidb-prod with restart policy is true, nodes: , roles: tidb.
Do you want to continue? [y/N]:(default=N) y

  • [ Serial ] - SSHKeySet: privateKey=/home/tidb/.tiup/storage/cluster/clusters/tidb-prod/ssh/id_rsa, publicKey=/home/tidb/.tiup/storage/cluster/clusters/tidb-prod/ssh/id_rsa.pub
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.45
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.45
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.45
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.43
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.46
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.45
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.41
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.46
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.42
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.46
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.47
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.47
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.47
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.47
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.48
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.48
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.46
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.48
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.41
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.42
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.43
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.43
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.42
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.44
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.49
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.50
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.41
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.44
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.42
  • [Parallel] - UserSSH: user=tidb, host=172.20.45.41
  • [Parallel] - UserSSH: user=tidb, host=172.20.45.41
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.41
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.48
  • [Parallel] - UserSSH: user=tidb, host=172.20.45.41
  • [Parallel] - UserSSH: user=tidb, host=172.20.46.43
  • [ Serial ] - UpdateTopology: cluster=tidb-prod
  • Refresh instance configs
    • Regenerate config pd -> 172.20.46.41:2379 … Error
    • Regenerate config pd -> 172.20.46.42:2379 … Error
    • Regenerate config pd -> 172.20.46.43:2379 … Error
    • Regenerate config tikv -> 172.20.46.45:20160 … Error
    • Regenerate config tikv -> 172.20.46.45:20161 … Error
    • Regenerate config tikv -> 172.20.46.45:20162 … Error
    • Regenerate config tikv -> 172.20.46.45:20163 … Error
    • Regenerate config tikv -> 172.20.46.46:20160 … Error
    • Regenerate config tikv -> 172.20.46.46:20161 … Error
    • Regenerate config tikv -> 172.20.46.46:20162 … Error
    • Regenerate config tikv -> 172.20.46.46:20163 … Error
    • Regenerate config tikv -> 172.20.46.47:20160 … Error
    • Regenerate config tikv -> 172.20.46.47:20161 … Error
    • Regenerate config tikv -> 172.20.46.47:20162 … Error
    • Regenerate config tikv -> 172.20.46.47:20163 … Error
    • Regenerate config tikv -> 172.20.46.48:20160 … Error
    • Regenerate config tikv -> 172.20.46.48:20161 … Error
    • Regenerate config tikv -> 172.20.46.48:20162 … Error
    • Regenerate config tikv -> 172.20.46.48:20163 … Error
    • Regenerate config tidb -> 172.20.46.41:4000 … Error
    • Regenerate config tidb -> 172.20.46.41:4001 … Error
    • Regenerate config tidb -> 172.20.46.42:4000 … Error
    • Regenerate config tidb -> 172.20.46.42:4001 … Error
    • Regenerate config tidb -> 172.20.46.43:4000 … Error
    • Regenerate config tidb -> 172.20.46.43:4001 … Error
    • Regenerate config tidb -> 172.20.46.44:4000 … Error
    • Regenerate config tidb -> 172.20.46.44:4001 … Error
    • Regenerate config tiflash -> 172.20.46.49:9000 … Error
    • Regenerate config tiflash -> 172.20.46.50:9000 … Error
    • Regenerate config cdc -> 172.20.46.41:8300 … Error
    • Regenerate config cdc -> 172.20.46.42:8300 … Error
    • Regenerate config cdc -> 172.20.46.43:8300 … Error
    • Regenerate config prometheus -> 172.20.45.41:9090 … Error
    • Regenerate config grafana -> 172.20.45.41:3000 … Error
    • Regenerate config alertmanager -> 172.20.45.41:9093 … Error

Error: init config failed: 172.20.46.41:2379: transfer from /home/tidb/.tiup/storage/cluster/clusters/tidb-prod/config-cache/pd-172.20.46.41-2379.service to /tmp/pd_a37c8bcb-8d5e-4909-a282-6df293da4529.service failed: failed to scp /home/tidb/.tiup/storage/cluster/clusters/tidb-prod/config-cache/pd-172.20.46.41-2379.service to tidb@172.20.46.41:/tmp/pd_a37c8bcb-8d5e-4909-a282-6df293da4529.service: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

Verbose debug logs has been written to /home/tidb/.tiup/logs/tiup-cluster-debug-2022-01-10-10-27-17.log.
Error: run /home/tidb/.tiup/components/cluster/v1.8.1/tiup-cluster (wd:/home/tidb/.tiup/data/Su4qQZC) failed: exit status 1

  1. TiUP Cluster Display 信息

  2. TiUP Cluster Edit Config 信息

  3. TiDB- Overview 监控

  • 对应模块日志（包含问题前后1小时日志）
2

如果你的中控到 各各服务节点已经做好了免密
可以使用 --ssh system 使用 系统 ssh 来进行连接验证

2 个赞
3

使用tiup cluster reload --ssh system tidb-prod -R tidb命令，问题解决，感谢！

1 个赞
4

:+1::+1::+1:又学到了

5

太感谢了，牛