8.0.0 tiup cluster start tidb-hbdzj --init Unable to Start Cluster

Translated
1

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

Original topic: 8.0.0 tiup cluster start tidb-hbdzj --init 无法启动集群

| username: TiDBer_5KtKPuFd

[TiDB Usage Environment] Production Environment / Testing / PoC
Testing
[TiDB Version]
8.0.0
[Reproduction Path] What operations were performed when the issue occurred
tiup cluster start tidb-hbdzj --init
[Encountered Issue: Issue Phenomenon and Impact]
failed to start tidb: failed to start: 192.168.0.68 tidb-4000.service, please check the instance’s log(/home/bigdata/tidb-deploy/tidb-4000/log) for more detail.: timed out waiting for port 4000 to be started after 2m0s
[Resource Configuration] Enter TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]

2
| username: DBAER | Original post link

Please provide the specific logs mentioned in the prompt.

3
| username: TiDBer_QYr0vohO | Original post link

Check the tidb-server logs.

4
| username: srstack | Original post link

Feeling like there aren’t enough resources? TiDB won’t start?

5
| username: TIDB-Learner | Original post link

First, check the deployment environment. Official documentation:
TiDB Environment and System Configuration Check | PingCAP Documentation Center TiDB 环境与系统配置检查 | PingCAP 文档中心

6
| username: zhanggame1 | Original post link

display to check the cluster status

7
| username: 随缘天空 | Original post link

Your machine configuration is probably too low to meet the official requirements. Based on the components you have installed, check the hardware configuration of each machine to see if it meets the minimum requirements.

8
| username: Jack-li | Original post link

Without logs, it’s difficult to analyze. :face_with_monocle:

9
| username: 小于同学 | Original post link

Please send the logs.

10
| username: 健康的腰间盘 | Original post link

The same issue, it shouldn’t be the configuration. Carefully check the Protobuf file, and make sure there are no hidden Windows newline characters.

11
| username: 不想干活 | Original post link

Please share the log from /home/bigdata/tidb-deploy/tidb-4000/log.

12
| username: TiDBer_QYr0vohO | Original post link

It is estimated that there is not enough memory, causing some components to fail to start.

13
| username: yytest | Original post link

Need to check the logs.

14
| username: zhaokede | Original post link

Timed out waiting for port 4000

15
| username: TiDBer_rvITcue9 | Original post link

Most likely, the memory is insufficient.

16
| username: 数据库真NB | Original post link

According to the official document, PingCAP Documentation Center TiDB 环境与系统配置检查 | PingCAP 文档中心, please check it yourself.

17
| username: yytest | Original post link

Is there any relevant error information in the logs?

18
| username: Jellybean | Original post link

When there is an issue with a node failing to start during cluster deployment, it is usually due to incorrect configuration items or content. Go to the path /home/bigdata/tidb-deploy/tidb-4000/log on the machine 192.168.0.68, check the ERROR log to identify the relevant cause, and then make targeted adjustments.