TiDB 6.2 TiDB Component Fails to Start

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tidb6.2 tidb组件启动不了

| username: 谢斌1204

tidb 6.2 cannot start the tidb component, it prompts timeout
Error: failed to start tidb: failed to start: 10.96.129.228 tidb-4000.service, please check the instance’s log(/data/tidb/tidb-deploy/tidb-4000) for more detail.: timed out waiting for port 4000 to be started after 2m0s

2022-09-02T12:16:41.996+0800 DEBUG retry error {“error”: “operation timed out after 2m0s”}
2022-09-02T12:16:41.996+0800 DEBUG TaskFinish {“task”: “Start new instances”, “error”: “failed to start tidb: failed to start: 10.96.129.228 tidb-4000.service, please check the instance’s log(/data/tidb/tidb-deploy/tidb-4000) for more detail.: timed out waiting for port 4000 to be started after 2m0s”, “errorVerbose”: “timed out waiting for port 4000 to be started after 2m0s
github.com/pingcap/tiup/pkg/cluster/module.(*WaitFor).Execute
\tgithub.com/pingcap/tiup/pkg/cluster/module/wait_for.go:91
github.com/pingcap/tiup/pkg/cluster/spec.PortStarted
\tgithub.com/pingcap/tiup/pkg/cluster/spec/instance.go:116
github.com/pingcap/tiup/pkg/cluster/spec.(*BaseInstance).Ready
\tgithub.com/pingcap/tiup/pkg/cluster/spec/instance.go:148
github.com/pingcap/tiup/pkg/cluster/operation.startInstance
\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:404
github.com/pingcap/tiup/pkg/cluster/operation.StartComponent.func1
\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:533
golang.org/x/sync/errgroup.(*Group).Go.func1
\tgolang.org/x/sync@v0.0.0-20220513210516-0976fa681c29/errgroup/errgroup.go:74
runtime.goexit
\truntime/asm_amd64.s:1571
failed to start: 10.96.129.228 tidb-4000.service, please check the instance’s log(/data/tidb/tidb-deploy/tidb-4000) for more detail.
failed to start tidb”}
2022-09-02T12:16:41.996+0800 INFO Execute command finished {“code”: 1, “error”: “failed to start tidb: failed to start: 10.96.129.228 tidb-4000.service, please check the instance’s log(/data/tidb/tidb-deploy/tidb-4000) for more detail.: timed out waiting for port 4000 to be started after 2m0s”, “errorVerbose”: “timed out waiting for port 4000 to be started after 2m0s
github.com/pingcap/tiup/pkg/cluster/module.(*WaitFor).Execute
\tgithub.com/pingcap/tiup/pkg/cluster/module/wait_for.go:91
github.com/pingcap/tiup/pkg/cluster/spec.PortStarted
\tgithub.com/pingcap/tiup/pkg/cluster/spec/instance.go:116
github.com/pingcap/tiup/pkg/cluster/spec.(*BaseInstance).Ready
\tgithub.com/pingcap/tiup/pkg/cluster/spec/instance.go:148
github.com/pingcap/tiup/pkg/cluster/operation.startInstance
\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:404
github.com/pingcap/tiup/pkg/cluster/operation.StartComponent.func1
\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:533
golang.org/x/sync/errgroup.(*Group).Go.func1
\tgolang.org/x/sync@v0.0.0-20220513210516-0976fa681c29/errgroup/errgroup.go:74
runtime.goexit
\truntime/asm_amd64.s:1571
failed to start: 10.96.129.228 tidb-4000.service, please check the instance’s log(/data/tidb/tidb-deploy/tidb-4000) for more detail.
failed to start tidb”}

2
| username: Ming | Original post link

You can manually start TiDB on the node to see what it reports.

3
| username: alfred | Original post link

Is the network connected for “timed out waiting for port 4000 to be started after 2m0s”?

4
| username: gary | Original post link
  1. You can check if the deployment and data directories have the necessary permissions.
  2. Manually execute the startup script located at /data/tidb/tidb-deploy/tidb-4000/scripts/.
5
| username: 谢斌1204 | Original post link

No response when executing.

6
| username: 谢斌1204 | Original post link

Network communication

7
| username: 谢斌1204 | Original post link

No errors.

8
| username: gary | Original post link

Have the deployment and data directory permissions been confirmed?

9
| username: OnTheRoad | Original post link

When I was deploying TiUniManager, I encountered a timeout issue with the Elasticsearch component startup. After upgrading the host configuration, it started normally. What is the configuration of your TiDB host?

10
| username: zhouzeru | Original post link

I have encountered this as well, and I started it manually.

11
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.