TiDB Deployment Successful but Unable to Start

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

Original topic: Tidb 部署成功就是无法启动

| username: Cheriston

Excuse me, what’s going on?

| username: Kongdom | Original post link

Is it a local environment? You can first execute tiup cluster display to check the cluster status. When resources are insufficient, it may start up relatively slowly. You can also check the log files under TiDB as suggested, not the ones under the cluster.

| username: Cheriston | Original post link

Thank you
Thank you
Thank you
Thank you

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

Guessing the resources are not enough? It has already started up to TiDB, and everything else is up and running…

| username: zhanggame1 | Original post link

Is there a parameter file for deployment?
You can also check the error logs on the TiDB nodes.

| username: 大飞哥online | Original post link

101 has been starting for over 2 minutes. Check the resource environment to see if there is any contention or resource issues.

| username: TiDBer_vfJBUcxl | Original post link

Log in to the TiDB host at 192.168.233.101 and check the logs.

| username: TiDB_C罗 | Original post link

I have encountered insufficient resources in a virtual machine environment.

| username: 天蓝色的小九 | Original post link

It might be due to insufficient resources.

| username: zhanggame1 | Original post link

Check the available memory to see if there is a shortage of memory.

| username: Kongdom | Original post link

:yum: So, was it resolved in the end?

| username: redgame | Original post link

Insufficient resources

| username: 昵称想不起来了 | Original post link

The system resources might be insufficient. Check the system status at that time and try allocating more resources.

| username: hey-hoho | Original post link

Log in to the 101 node where the error occurred and check the TiDB logs at /tidb-deploy/tidb-1/log. The problem will become very clear.

| username: ajin0514 | Original post link

Log in to the TiDB host at 192.168.233.101 and check the logs; it seems that resources are insufficient.