Open zengod1205 opened 6 years ago
Yes the advise to check on DNS is legit, ability to access via browser especially Chrome masked the problem because chrome use built-in dns which is google dns (8.8.8.8) by default and doing dns prefetching http://hanxue-it.blogspot.sg/2014/04/how-to-disable-dns-prefetching-in.html?m=1
Lots of reported issues related to DNS for Ubuntu 17++ onwards due to the use of systemd-resolved. Be sure to check that too. https://www.hecticgeek.com/2017/04/ubuntu-17-04-systemd-dns-issues/
Guys, I've mentioned that host PC pings & opens those links fine. Google DNS and Cloudflare DNS were tried. It's not the issue with resolving host names. Tried via two different VPNs and ISP directly. And all DNS are pushed from VPN server, so the host machine and virtual one with docker on board have to use only pushed DNS.
This is a local DNS lookup problem. I think there is some sort of rate limiting in play in your DNS setup.
Prerequisites
Are you running the latest version? yes
Are you running the docker image or did you built from source? docker image
Did you check the README.md for steps to run? yes
Did you check logs? (either in console or in
_logs
directory) logs directory is emptyDescription
The miner stops running, looses all peers, or even doesn't begin collecting blocks. The same command works fine on other PCs on Win110 and Ubuntu. Currently getting described error on Win10 latest. Host machine, or docker cli can ping all the resources f.e. 'https://nodes.wavesnodes.com/blocks/height'
Steps to Reproduce
Expected behavior:
mining blocks on testnet
Actual behavior: [seems, that miner looses connectivity with network. Tried direct connection and different VPN setups, no luck. The same connections work on other PCs]
Versions
Application (required)
Environment (optional but helpful)
Logs