filecoin-project / filecoin-project/boost
[Support Ticket]: Boost UI not available after the first restart since v21
- Dominant language
- Go
- Stars
- 121
- Forks
- 79
- Avg merge
- 10d 14h
- Merged PRs (30d)
- 1
Description
### Boost component
- [ ] boost daemon - storage providers
- [ ] boost client
- [X] boost UI
- [ ] boost data-transfer
- [ ] boost index-provider
- [ ] booster-http
- [ ] booster-bitswap
- [ ] LID Database - Yugabyte/LevelDB
- [ ] boostd-data
- [ ] Other
### Boost Version
```text
~# boostd --version
boostd version 2.1.1+mainnet+git.e9d18ac
```
### Describe the problem
miner restart initiated an unintended restart of boostd by systemd. Till that moment it looked fine.
After starting , UI does not appear even after a long time.
```
root@filecoin:~# ss -nalp | grep boostd
udp UNCONN 0 0 0.0.0.0:48705 0.0.0.0:* users:(("boostd",pid=941177,fd=60))
tcp LISTEN 0 4096 0.0.0.0:24001 0.0.0.0:* users:(("boostd",pid=941177,fd=32))
```
### Logging Information
```text
# boostd log list
Error: getting boost api: cannot dial address ws://127.0.0.1:8787/rpc/v0 for dial tcp 127.0.0.1:8787: connect: connection refused: dial tcp 127.0.0.1:8787: connect: connection refused```
attaching systemd's first 400 lines of log in the next section
```
### Repo Steps
systemd startup log
[start-400.log](https://github.com/filecoin-project/boost/files/13664381/start-400.log)
Contributor guide
Research direction
Start by reading the attached start-400.log and checking the boostd startup path around the failed ws://127.0.0.1:8787/rpc/v0 connection. Reproduce the systemd-initiated restart and determine whether the boost UI becomes available afterward; done means the UI is reachable after the first restart and the reported connection refusal is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100