lambdaclass / lambdaclass/lambda_ethereum_consensus
Go panic: UDP address already in use
Open
Nobody has claimed this yet.
bug
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
The go libp2p module gets this error and the node doesn't recover, but process still lives.
panic: listen udp 0.0.0.0:9000: bind: address already in use
goroutine 1 [running]:
libp2p_port/internal/utils.PanicIfError(...)
/libp2p_port/internal/utils/utils.go:19
libp2p_port/internal/discovery.NewDiscoverer(0x40002e43d0?, 0x400023a640, 0x400001be80)
/libp2p_port/internal/discovery/discovery.go:34 +0x45c
main.commandServer()
/libp2p_port/main.go:74 +0x138
main.main()
/libp2p_port/main.go:90 +0x1c
As a quick hypothesis, it might be a clean-up problem when the libp2p genserver restarts.
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 with the stack-trace locations in internal/utils/utils.go:19, internal/discovery/discovery.go:34, and main.go:74-90. Reproduce the UDP port conflict and inspect how the discoverer behaves when the libp2p genserver restarts; done means the node no longer remains alive in a panicked state when port 9000 is already in use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100