-
Notifications
You must be signed in to change notification settings - Fork 847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNS Discovery exceptions #5212
Comments
There was this recent change to remove deprecated EF bootnodes #5194 (this hasn't been released yet), and since then also then the discv4 dns list has been updated (it's updated daily) https://github.com/ethereum/discv4-dns-lists/tree/master/all.mainnet.ethdisco.net I am seeing the occasional Timeout / IOException as you are, at the following rates with these different versions of Besu - I thought that the occasional timeout was expected when contacting so many DNS servers - @gezero I see you spent some time investigating this in #3044 - is this error occasionally expected or has something changed? |
Fwiw, I get the error constantly and it doesn't connect to any nodes on 23.1.1 |
Hi @Xexr, would you be able to provide us with more logs? Maybe with Debug enabled. Also, what is your machine configuration? |
I was seeing this on 23.1.2 as well.
|
and also on 23.1.3
|
I spoke with @zapaz on ethstaker besu-helpdesk discord: it was a Dappnode installation (so docker) and it wasn't possible for them to sync once it started happening so they had to abandon besu. Also, dns resolve unix command was working, it was just besu that had the issue. Note, Dappnode doesn't have 23.4.0 available yet so that couldn't be tested at the time. |
Maybe related #4678 |
Potential config fix - increase rate limit for DNS requests - #4258 |
Just to update (this is ruk.eth from above). Now that it is full synced, it is no longer doing this. |
Some potential improvements/investigations to do over here #5472 |
I have BESU native service, running on 22.04, stand-alone machine with only this Execution Client running. Besu version: 23.4.1 I only encountered this after a restart, where I restarted my Besu and Teku machines at the same time. Happened on and off for about 5 minutes, and I have not seen it since: Jun 16 05:16:44 anon besu[821]: 2023-06-16 05:16:44.355+00:00 | Timer-0 | WARN | DNSResolver | I/O exception contacting remote DNS server when resolving HERAIXIT5KIQMKQL62ALL6.all.mainnet.ethdisco.net |
I am running Ubuntu 22.04.2 LTS with Nimbus 23.6.0 and Besu 23.4.1. I am running an Eero mesh wifi system. My validator just became active a few days ago. It was running fine for 24 hours, so I installed MEVBoost. Nimbus and MEVBoost seemed to be working fine, but Besu started showing a DNS Resolver error. After switching my DNS Resolver to 1.1.1.1, everything went back to working fine. It ran flawlessly for 24 hours. I hadn't touched my NUC but I started receiving more errors on Besu. See below. Jun 26 20:05:04 CrouchNUC besu[4946]: 2023-06-26 20:05:04.894-04:00 | main | INFO | NetworkRunner | Supported capabilities: [eth/63, eth/64, eth/65, eth/66, eth/67, eth/68], [snap/1] |
I also see the following when I check my 1.1.1.1 DNS Resolver. Debug Information Connectivity to Resolver IP Addresses |
Same problem here,
|
silenced DNS query error warnings #6458 |
Originally posted by @Xexr in #3044 (comment)
Getting this issue again on 23.1.1, reverting to 23.1.0 resolves the problem.
Log below...
The text was updated successfully, but these errors were encountered: