Tidb-server failed to start

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

Original topic: tidb-server启动失败

| username: Kamner

[TiDB Usage Environment] Testing
[TiDB Version] v6.0.0
[Reproduction Path] What operations were performed to cause the issue

[Encountered Issue: Problem Phenomenon and Impact]

The virtual machine experienced physical server drift, and the cluster restart reported the following error:

The cluster status is as follows:

/tidb/tiup/logs/tiup-cluster-debug-2024-04-02-10-37-00.log log is as follows:

/tidb/tidb-deploy/tidb-4000/log/tidb.log log is as follows:

| username: TiDBer_jYQINSnf | Original post link

Where is the final fatal log of TiDB?

| username: zhanggame1 | Original post link

What is the status of tiup cluster display?

| username: Kamner | Original post link

The image is not visible. Please provide the text you need translated.

| username: Kamner | Original post link

I forgot to add.

| username: WalterWj | Original post link

Can your TiDB access port 20160 on 13?

| username: TiDBer_jYQINSnf | Original post link

Can’t access PD? Try manually accessing PD and executing ‘store’ to see if it works properly.
Also, are there only 2 TiKV nodes?

| username: TIDB-Learner | Original post link

  1. Network latency is unstable, check the network/ports.
  2. Server resource issues.
  3. Check configurations, such as topology, especially custom projects.
| username: mono | Original post link

The downtime is too long, it has been kicked out of the cluster!

| username: zhanggame1 | Original post link

First, check if the network is fully connected. Ping each machine one by one.

| username: 像风一样的男子 | Original post link

Why are there only 2 nodes? There’s no high availability.
The simplest way is to scale down the failed PD and TiDB nodes and then scale them back up.

| username: TiDBer_vZIeuSNY | Original post link

You can check if the swap, firewall, and selinux settings are different from before after the reboot.

| username: Soysauce520 | Original post link

Is the machine network connected? The number of KVs in the picture is also incorrect. How did it become two?

| username: tidb菜鸟一只 | Original post link

The virtual machine has experienced physical server drift, and the following error occurred when restarting the cluster:

What does this mean? Has the server’s IP changed?

| username: Kamner | Original post link

TiDB access to 13 is not working:

But port 13 exists, and the cluster status shows it is running:

| username: Kamner | Original post link

VM migration, IP unchanged

| username: Jolyne | Original post link

Has there been a change in the network policy? Please check.

| username: Kamner | Original post link

TiDB can access port 22 of 13.

| username: Kamner | Original post link

Another TiKV node 12 has error logs:

| username: TiDBer_jYQINSnf | Original post link

Check if TiKV is running normally on 13. If it’s not running, look at the error messages. If it is running, check the network.