使用root用户安装TIDB,部署完成后,启动失败,详见内文

Starting component pd
Starting instance pd 10.46.137.23:2379
Start pd 10.46.137.23:2379 success
Starting component node_exporter
Starting instance 10.46.137.23
Start 10.46.137.23 success
Starting component blackbox_exporter
Starting instance 10.46.137.23
Start 10.46.137.23 success
Starting component tikv
Starting instance tikv 10.46.137.23:20160
Start tikv 10.46.137.23:20160 success
Starting component tidb
Starting instance tidb 10.46.137.23:4000
retry error: operation timed out after 2m0s
tidb 10.46.137.23:4000 failed to start: timed out waiting for port 4000 to be started after 2m0s, please check the log of the instance

Error: failed to start tidb: tidb 10.46.137.23:4000 failed to start: timed out waiting for port 4000 to be started after 2m0s, please check the log of the instance: timed out waiting for port 4000 to be started after 2m0s

Verbose debug logs has been written to /home/tidb/logs/tiup-cluster-debug-2020-11-10-16-15-41.log.
Error: run /root/.tiup/components/cluster/v1.2.3/tiup-cluster (wd:/root/.tiup/data/SFvLfLt) failed: exit status 1

看下 tidb log 是否有详细内容

日志内容如下,循环提示启动失败,没有具体的失败原因介绍,在启动之前已经检查了4000端口是闲置的,依然报错。
2020-11-10T16:22:22.253+0800 DEBUG retry error: operation timed out after 2m0s
2020-11-10T16:22:22.253+0800 ERROR tidb 10.46.137.23:4000 failed to start: timed out waiting for port 4000 to be started after 2m0s, please check the log of the instance
2020-11-10T16:22:22.253+0800 DEBUG TaskFinish {“task”: “StartCluster”, “error”: “failed to start tidb: \ttidb 10.46.137.23:4000 failed to start: timed out waiting for port 4000 to be started after 2m0s, please check the log of the instance: timed out waiting for port 4000 to be started after 2m0s”, “errorVerbose”: “timed out waiting for port 4000 to be started after 2m0s\ngithub.com/pingcap/tiup/pkg/cluster/module.(*WaitFor).Execute\ \tgithub.com/pingcap/tiup@/pkg/cluster/module/wait_for.go:90\ github.com/pingcap/tiup/pkg/cluster/spec.PortStarted\ \tgithub.com/pingcap/tiup@/pkg/cluster/spec/instance.go:101\ github.com/pingcap/tiup/pkg/cluster/spec.(*BaseInstance).Ready\ \tgithub.com/pingcap/tiup@/pkg/cluster/spec/instance.go:132\ github.com/pingcap/tiup/pkg/cluster/operation.startInstance\ \tgithub.com/pingcap/tiup@/pkg/cluster/operation/action.go:564\ github.com/pingcap/tiup/pkg/cluster/operation.StartComponent.func1\ \tgithub.com/pingcap/tiup@/pkg/cluster/operation/action.go:679\ golang.org/x/sync/errgroup.(*Group).Go.func1\ \tgolang.org/x/sync@v0.0.0-20190911185100-cd5d95a43a6e/errgroup/errgroup.go:57\ runtime.goexit\ \truntime/asm_amd64.s:1357\ \ttidb 10.46.137.23:4000 failed to start: timed out waiting for port 4000 to be started after 2m0s, please check the log of the instance\ failed to start tidb”}
2020-11-10T16:22:22.254+0800 INFO Execute command finished {“code”: 1, “error”: “failed to start tidb: \ttidb 10.46.137.23:4000 failed to start: timed out waiting for port 4000 to be started after 2m0s, please check the log of the instance: timed out waiting for port 4000 to be started after 2m0s”, “errorVerbose”: “timed out waiting for port 4000 to be started after 2m0s\ngithub.com/pingcap/tiup/pkg/cluster/module.(*WaitFor).Execute\ \tgithub.com/pingcap/tiup@/pkg/cluster/module/wait_for.go:90\ github.com/pingcap/tiup/pkg/cluster/spec.PortStarted\ \tgithub.com/pingcap/tiup@/pkg/cluster/spec/instance.go:101\ github.com/pingcap/tiup/pkg/cluster/spec.(*BaseInstance).Ready\ \tgithub.com/pingcap/tiup@/pkg/cluster/spec/instance.go:132\ github.com/pingcap/tiup/pkg/cluster/operation.startInstance\ \tgithub.com/pingcap/tiup@/pkg/cluster/operation/action.go:564\ github.com/pingcap/tiup/pkg/cluster/operation.StartComponent.func1\ \tgithub.com/pingcap/tiup@/pkg/cluster/operation/action.go:679\ golang.org/x/sync/errgroup.(*Group).Go.func1\ \tgolang.org/x/sync@v0.0.0-20190911185100-cd5d95a43a6e/errgroup/errgroup.go:57\ runtime.goexit\ \truntime/asm_amd64.s:1357\ \ttidb 10.46.137.23:4000 failed to start: timed out waiting for port 4000 to be started after 2m0s, please check the log of the instance\ failed to start tidb”}

你好这是 tiup debug 日志, 辛苦看下 tidb.log

已经解决了,重启服务器后,再次start成功了,谢谢

:+1: