output the latest log of component when failed to start
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
question from user:
tiup 替换 tidb-server 可执行文件后，tiup cluster start出现 “Starting component tidb
Starting instance tidb 172.16.5.69:4000
tidb 172.16.5.69:4000 failed to start: timed out waiting for port 4000 to be started after 1m0s”
可是目标机器上 lsof -i:4000 确实没有被占用，那是怎么回事呢？
make the user know why failling to start more easily
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the tiup cluster start path for the timeout while starting a tidb-server instance. Find where the failure message is assembled and determine how the component's latest log can be surfaced. Done means a failed start explains the cause using the latest available component log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100