TiDB 4000 Port Fails to Start

Translated
1

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

Original topic: tidb 4000端口无法启动

| username: TiDBer_lF5whaJ3

[Test Environment for TiDB] Testing
[TiDB Version] v6.1.0
[Reproduction Path] Install TiDB environment, TiDB port 4000 fails to start
[Encountered Problem: Symptoms and Impact] TiDB init fails to start
[Resource Configuration]
[Attachment: Screenshot/Log/Monitoring]

image
image1437×477 50.4 KB

2
| username: 裤衩儿飞上天 | Original post link

The error is very clear: region is unavailable.
Are all the TiKV nodes up?
Is there any region loss?

3
| username: TiDBer_lF5whaJ3 | Original post link

TiKV has only one node, and it is up.

4
| username: 裤衩儿飞上天 | Original post link

Is it a single replica? Check if there are any errors reported by TiKV and PD?

5
| username: TiDBer_lF5whaJ3 | Original post link

Found the cause of the problem. The time on the two nodes was inconsistent. After calibration, it worked.

6
| username: Kongdom | Original post link

NTP time synchronization needs to be deployed.

7
| username: TiDBer_lF5whaJ3 | Original post link

After calibrating the time, it works, but creating the database still reports the same error.
TiKV log:

image
image1446×693 76.8 KB

PD log:
image
image1438×837 92.4 KB

8
| username: WalterWj | Original post link

Is the environment not clean? There was a cluster before, and it was not cleaned up properly, leading to the reuse of directories during the new deployment.

9
| username: 裤衩儿飞上天 | Original post link

First, clean up the environment before redeploying, or use different directories and ports. Perform a check before deployment.

10
| username: liuis | Original post link

I encountered this before as well. Just clean up the environment and redeploy.

11
| username: system | Original post link

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