Error starting TiDB: failed to start: 192.168.137.130 tidb-4000.service, please check the instance's log (/opt/tidb-deploy/tidb-4000/log) for more details: timed out waiting for port 4000 to start after 2m0s

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

Original topic: 启动tidb时报错failed to start tidb: failed to start: 192.168.137.130 tidb-4000.service, please check the instance’s log(/opt/tidb-deploy/tidb-4000/log) for more detail.: timed out waiting for port 4000 to be started after 2m0s

| username: TiDBer_YL9tqf3q

[Test Environment] Testing environment openEuler22.03
[TiDB Version] v6.4.0
[Reproduction Path] First-time installation of single-node TiDB
[Encountered Issue: Phenomenon and Impact] TiDB fails to start, reporting “timed out waiting for port 4000 to be started after 2m0s”
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

[2022/11/23 17:37:00.621 +08:00] [INFO] [global.go:34] [“daemon became owner”] [id=63e1b010-bc76-4975-a0f6-58710090de56] [daemon-id=LogBackup::Advancer]
[2022/11/23 17:38:04.889 +08:00] [INFO] [region_request.go:794] [“mark store’s regions need be refill”] [id=2] [addr=192.168.137.130:20162] [error=“context deadline exceeded”]
[2022/11/23 17:38:04.889 +08:00] [WARN] [session.go:989] [“can not retry txn”] [label=internal] [error=“context deadline exceeded”] [IsBatchInsert=false] [IsPessimistic=false] [InRestrictedSQL=true] [tidb_retry_limit=10] [tidb_disable_txn_auto_retry=true]
[2022/11/23 17:38:04.889 +08:00] [WARN] [session.go:1005] [“commit failed”] [“finished txn”=“Txn{state=invalid}”] [error=“context deadline exceeded”]
[2022/11/23 17:38:04.890 +08:00] [WARN] [session.go:2191] [“run statement failed”] [schemaVersion=18] [error=“context deadline exceeded”] [session=“{\n "currDBName": "mysql",\n "id": 0,\n "status": 2,\n "strictMode": true,\n "user": null\n}”]
[2022/11/23 17:38:04.890 +08:00] [FATAL] [bootstrap.go:2192] [“mustExecute error”] [error=“context deadline exceeded”] [stack=“github.com/pingcap/tidb/session.mustExecute\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:2192\ngithub.com/pingcap/tidb/session.insertBuiltinBindInfoRow\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:1513\ngithub.com/pingcap/tidb/session.initBindInfoTable\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:1509\ngithub.com/pingcap/tidb/session.doDDLWorks\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:2044\ngithub.com/pingcap/tidb/session.bootstrap\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:455\ngithub.com/pingcap/tidb/session.runInBootstrapSession\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:3002\ngithub.com/pingcap/tidb/session.BootstrapSession\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:2875\nmain.createStoreAndDomain\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/tidb-server/main.go:310\nmain.main\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/tidb-server/main.go:211\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250”]

| username: Jiawei | Original post link

You can check if the machine configuration is too low. You can also check if the system’s IO and CPU are already fully utilized when you start tiup.

| username: TiDBer_YL9tqf3q | Original post link

Configured to 4 cores, 16 threads, and 16GB of memory, but it’s still not working. I see that the usage rate is not high either.


| username: 我是咖啡哥 | Original post link

Maybe restarting or reinstalling will fix it :joy:

| username: TiDBer_YL9tqf3q | Original post link

I reinstalled a virtual machine, increased the configuration, and reinstalled TiDB. It indeed worked. Thank you, everyone.

| username: system | Original post link

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