Startup Error

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

Original topic: 启动报错

| username: TiDBer_NNPScbiY

[TiDB Usage Environment] /Test/
[TiDB Version] 6.5.2
[Reproduction Path] Frequently reports connection timeout after deployment and startup; then deletes a few connections and reports 4000 no route host
[Encountered Problem: Phenomenon and Impact]
[Resource Configuration]
[Attachment: Screenshot/Log/Monitoring]

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

Are all the cluster nodes functioning normally?

| username: TiDBer_NNPScbiY | Original post link

It never started up; but if installed on a single machine, it can start up.

| username: xfworld | Original post link

It looks like it didn’t start properly, or the network is down.

| username: TiDBer_NNPScbiY | Original post link

Yes, it didn’t start normally. I tried to restart TiDB, but it failed to start and timed out.

| username: TiDBer_NNPScbiY | Original post link

The network is connected, and the ports are not occupied.

| username: Hacker007 | Original post link

Show me the logs.

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

Check if the firewall is enabled.

| username: TiDBer_NNPScbiY | Original post link

The firewall is not enabled~~

| username: TiDBer_NNPScbiY | Original post link

Sorry, I can’t translate images. Please provide the text you need translated.

| username: TiDBer_NNPScbiY | Original post link

The first image shows the startup error, and below is the log of the TiDB node that encountered the error.

| username: xfworld | Original post link

The logs describe that the networks 203 and 204 are not connected.

For hybrid deployment, you need to refer to the official documentation for adjustments, which can be quite troublesome.

If it’s just for experience and you don’t have enough machines, deploying 1 PD + 1 TiKV + 1 TiDB will suffice.

| username: TiDBer_NNPScbiY | Original post link

The network seems fine, both ping and telnet are working.

| username: xfworld | Original post link

No matter how you look at it, there shouldn’t be any problems; otherwise, high concurrency scenarios would be easily resolved…

How about strictly following the official documentation for environment setup during deployment?

| username: TiDBer_NNPScbiY | Original post link

The deployment method and configuration files are all according to the official configuration. Later, it didn’t work, so I changed the port, but it still doesn’t work~~~

| username: zhanggame1 | Original post link

First, check if the network is stable and if there is any packet loss.

| username: wzf0072 | Original post link

Refer to the “Simple Multi-Instance Configuration Template”.

| username: TiDBer_pkQ5q1l0 | Original post link

No route to host, telnet not working? Is the service not up? Also, check the gateway exit.

| username: zhanggame1 | Original post link

First, check if the network is stable and if there is any packet loss.

| username: TiDBer_NNPScbiY | Original post link

Problem solved, it was just a network issue~~~