smartcontractkit / smartcontractkit/chainlink
[NODE] Node exits if primary ETH_URL cannot be resolved
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.2k
- Forks
- 2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 202
Description
Description
If the DNS for primary ETH_URL cannot be resolved, the node exits with error error starting app: dial tcp: lookup <ETH_URL>: No address associated with hostname
Expected behavior: ChainLink node fails over to ETH_SECONDARY_URLS, if configured, and logs a WARN; otherwise logs an ERROR but keeps going and keeps trying.
Basic Information
- Operating System: Ubuntu 20.04
- Commit: Chainlink Node 0.10.4 at commit 1f76904abc1016d1d1c3946676a3fa125e33e550
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 node startup and the ETH_URL DNS resolution path, then inspect how ETH_SECONDARY_URLS and connection retries are handled. Reproduce an unresolvable primary URL and verify that configured secondary URLs are tried; otherwise the node should keep running, retry, and log WARN or ERROR as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, blockchain, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100