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
Improve DNS use from Ethstats #3792
Comments
networkaddress.cache.ttl |
@jflo hey Justin, can you ping me either on Discord or slack, I would like to chat about this ticket. One possible solution is to add system property networkaddress.cache.ttl=60 in Besu startup script. The other bit that I want to revalidate from you if the IP address of reverse proxy host is changing more often or the IP address of ethstats is changing more often? |
The other option is to modify the ethstats connecting code and set https://vertx.io/docs/apidocs/io/vertx/core/dns/AddressResolverOptions.html#setCacheMaxTimeToLive-int-. |
@non-fungible-nelson hey Matt, can you ping me regarding above issue, I want to get some further clarification from the user regarding the above issue and whether it is already sorted out or not. Cheers, Uzi. |
@jflo might know this - based on the mainnet shadow fork logs, this is likely also with the EF. @usmansaleem did you connect with @parithosh on the improvements? |
@siladu gave me an image to test out and that showed no ethstats issues, I'm honestly not sure which branch or fix he gave me to try, but perhaps he can chime in |
@parithosh That was probably cut againt the main branch that contained the ethstats related enhancements. Next Besu release should also contain these fixes. I am going to close this ticket, in case you face any issues, feel free to re-open this issue or create a new one. Thanks, /uzi |
Besu needs DNS/IP:Port whereas others allow for just DNS and let the reverse proxy route them to the correct port. My reverse proxy forwards the traffic to the new ethstats server, but Besu doesn't like that since it tries to send traffic to the port 3000 of the specified DNS server (doesn't touch the reverse proxy then).
So I can switch to IP:Port of the new server, but I'd say this is a QoL thing that should be fixed.
Acceptance Criteria
Steps to Reproduce (Bug)
Expected behavior: Reporting continues
Actual behavior: Reporting stops, error message in logs saying:
Failed to reach the ethstats server finishConnect(..) failed: Connection refused: ethstats.mainnetshadowfork3.ethdevops.io/164.92.169.47:3000
The text was updated successfully, but these errors were encountered: