Quote from: Claymore on October 07, 2016, 08:35:01 PM

Quote from: qqqq on October 07, 2016, 08:12:00 PM

I know what screenshot and log is. Just wanted to show the issue.

Finally I see the log.
From the log I see you have 3 ETH pools. After every 3 attempts miner switches to new pool. May be all pools have same IP, I don't know it, I have no idea why you cleared IP because 192.168.x.x addresses are not public, they are not routed. Anyway, 3 or 6 attempts mean that miner changed pool 1 or 2 times. To make a "clean" test, try to remove all settings from command line or config.dat and leave one pool in epools.txt as I described in previous message.
Also before starting miner it's a good idea that geth is working (and may be test it with some different miner). In my tests miner always starts working at first attempt.
I can add option to change the delay between attempts, but I'm not sure if it really necessary, you are the first person who want to have it.

I got ETC and ETH geth on different IP. It was off one geth specially for the reproduce the issue. But there is no issue actually. 3 attempts to connect and change the IP according epools.txt

Here my epools

POOL: http://192.168.100.88:8545
POOL: http://192.168.100.2:8545

Sometimes geth crushed due DDOS, so why i need 1 minute for that. Anyway request flag to reduce time between attempts to connect and ethman tray icon total hashmeter.