自己电脑部署的tidb宕机后无法启动

【 TiDB 使用环境】测试环境 【 TiDB 版本】V5.0 【遇到的问题】 集群无法启动 【复现路径】tiup cluster start tidb-test无法正常启动 【问题现象及影响】 [root@db01 bin]# tiup cluster start tidb-test tiup is checking updates for component cluster ... Starting component cluster`: /root/.tiup/components/cluster/v1.9.4/tiup-cluster /root/.tiup/components/cluster/v1.9.4/tiup-cluster start tidb-test
Starting cluster tidb-test…

  • [ Serial ] - SSHKeySet: privateKey=/root/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa, publicKey=/root/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa.pub
  • [Parallel] - UserSSH: user=tidb, host=192.168.100.5
  • [Parallel] - UserSSH: user=tidb, host=192.168.100.6
  • [Parallel] - UserSSH: user=tidb, host=192.168.100.5
  • [Parallel] - UserSSH: user=tidb, host=192.168.100.6
  • [Parallel] - UserSSH: user=tidb, host=192.168.100.3
  • [Parallel] - UserSSH: user=tidb, host=192.168.100.3
  • [Parallel] - UserSSH: user=tidb, host=192.168.100.3
  • [Parallel] - UserSSH: user=tidb, host=192.168.100.3
  • [Parallel] - UserSSH: user=tidb, host=192.168.100.5
  • [Parallel] - UserSSH: user=tidb, host=192.168.100.6
  • [Parallel] - UserSSH: user=tidb, host=192.168.100.3
  • [ Serial ] - StartCluster
    Starting component pd
    Starting instance 192.168.100.6:2379
    Starting instance 192.168.100.3:2379
    Starting instance 192.168.100.5:2379
    Start instance 192.168.100.5:2379 success
    Start instance 192.168.100.6:2379 success
    Start instance 192.168.100.3:2379 success
    Starting component tikv
    Starting instance 192.168.100.6:20160
    Starting instance 192.168.100.3:20160
    Starting instance 192.168.100.5:20160

Error: failed to start tikv: failed to start: 192.168.100.6 tikv-20160.service, please check the instance’s log(/tidb-deploy/tikv-20160/log) for more detail.: timed out waiting for port 20160 to be started after 2m0s

Verbose debug logs has been written to /root/.tiup/logs/tiup-cluster-debug-2022-04-22-16-01-58.log.
tikv.log (9.8 MB) 【附件】

1 个赞

部署的YAML文件,发一下
tiup cluster display tidb-test也发一下

1 个赞

确认一下:

  1. 192.168.100.6上防火墙是否关闭;
  2. 192.168.100.6上20160端口是否被占用;
1 个赞

20160端口被占用了,kill 一下试试

1 个赞

192.168.100.6:2379
192.168.100.3:2379
这两个都网络不通,防火墙?

1 个赞

果然是防火墙没关:joy:

1 个赞

是防火墙的问题

1 个赞

防火墙没关

1 个赞

防火墙没关。。。。。。

1 个赞

所以部署之前的准备工作还是要做的

1 个赞

:face_with_raised_eyebrow:这。。。太离谱了:joy:,果然最基本的常常是最容易忽视的

1 个赞

tiup cluster check可以使用起来

https://docs.pingcap.com/zh/tidb/stable/tiup-component-cluster-check#tiup-cluster-check

2 个赞

此话题已在最后回复的 1 分钟后被自动关闭。不再允许新回复。