Quote from: P00P135 on August 30, 2017, 11:26:39 AM

Quote from: Elange on August 30, 2017, 11:14:33 AM

Hi.

I noticed a couple of problems with the miner.

1. ethpool.org IP is not resolved correctly. Looks like eu1.ethpool.org IP is hard-coded or cached somewhere into miner. First connection attempt ALWAYS fails. Then, 20 sec wait, then, successful connect using a failover address. The first IP that miner tries to connect to (91.121.73.83) is not the IP which eu1.ethpool.org actually resolves to at the moment (188.165.235.31). My connections string is ./ethdcrminer64 -epool eu1.ethpool.org:3333 (Ubuntu)

2. I mine thru a typical wired router. When sometimes the router looses ISP connection it, as usual, serves its own error page to all clients. The miner, however, thinks it's a kind of a local proxy and attempts to continue mining. As no more new shares are found (because no more new jobs supplied), the miner thinks it's GPU failure ("Miner thread hangs") and activates the watchdog, instead of simply sitting there and waiting for internet connection to resume. This is not the right type of behavior, IMO.

Thanks!

I don't think this is a problem that needs to be addressed in the miner as it just sounds like you need to fix your internet Wink

1. Turns out, eu1.ethpool.org resolves to several IPs, the miner picks up the first one. The first one does not work (probably due to my location). So, this is a pool problem.
2. This does have to be solved. Watchdog should not be triggered in this case. Miner should differentiate between a mining proxy and a router.