Closed enriquemanuel closed 1 year ago
This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days.
This issue was closed because it has been stalled for 7 days with no activity.
please open this
I would like to add my observations on this kind of error message, in my case lead by:
"https://sync.invis.tools/eth/v2/debug/beacon/states/finalized": dial tcp: lookup sync.invis.tools: device or resource busy
OS: Ubuntu 22.04.2 LTS (Jammy Jellyfish) Architecture: aarch64 Official images:
As the error message already states, the underlying issue isn't directly related to Erigon itself. I can just guess that it may be an issue with the underlying Go libraries?
From my side, I could solve the issue by buildinng the container for all versions myself since v2.32.1 using:
docker build -f Dockerfile -t thorax/erigon:v<current version> .
and trying out the image, all with Go version 1.19.7. The error message disappers in all cases. Using the image from Docker Hub produces the above error message.
It seems like you're facing a similar issue related to Go DNS resolution. The problem can be solved by setting an environment variable.
Here's the command you can use to set the GODEBUG environment variable:
GODEBUG="netdns=go" ./bin/erigon --config ./config.toml
This will set the netdns value to go, which will use Go's implementation of DNS resolution instead of the system's implementation. This should help resolve the issue you're facing.
System information
Upgraded from: 2.28.1 Upgraded to: 2.30.0
OS: Debian Erigon is in Docker
Expected behaviour
Actual behaviour
Steps to reproduce the behaviour
have a network gateway that blocks connectivity to non approved sites and block the list there and Erigon wont start.
Before in
2.28.1
Erigon would start withand after the upgrade with the same set of CLI args it fails with
Backtrace
The issue was introduced when this change was added https://github.com/ledgerwatch/erigon/blob/5c3245d4e034606732573044a59ce793be1ceeea/cl/clparams/config.go#L189-L209 in PR https://github.com/ledgerwatch/erigon/pull/5761
Command Line Arguments:
More info
In the releases https://github.com/ledgerwatch/erigon/releases it doesn't state that it now needs to connect to those external sites by default nor it mentions the PR 5761 to be a requirement. Can that be bypassed? For sanity, any domain in that list isn't reachable from my production hosts unless I add a firewall rule, which is problematic since that list is not exhaustive and can change without any announcement; this alters the default behavior we had before but wasn't announced.
reverting to 2.28.1 allows us to start and run