Closed ghost closed 9 years ago
Which algorithm are you mining on (Scrypt, SHA-256, X11,...) ?
sha256 (bitcoin)
Do you have the same problem with other versions of cgminer ? Could you post your proxy configuration ?
no. cgminer/3.9.0 working fine --pool-append-worker-names false true true true --set-extranonce-subscribe true false false false --log-level OFF --pool-connection-retry-delay 500 --no-midstate
I will need the log file with a DEBUG loglevel. Thanks.
I just prepare it. You can download log at http://wikisend.com/download/467066/debug.log.gz TTL 7 days!
I do not know what is the problem. The proxy sends correctly the difficulty to the miner. For example: 2015-06-06 03:54:22,819 DEBUG [/xxxx:56588-Thread]:strat.mining.stratum.proxy.network.StratumConnection - /xxxx:56588. Send notification: {"id": null, "method": "mining.set_difficulty", "params": [1024.0]}
But indeed, your miner sends low difficulty shares to the proxy which are rejected by the pool. I do not see what I could do. Have you tryed to connect your miner directly on a pool ? If it works, could you send me a packet capture of the traffic between your miner and the pool (with tcpdump or wireshark) to look at the differences when the proxy is involved ?
Hi. I'm confused. While i recording tcpdump from pool, after about 3minutes i see 'Pool 3 set difficulty 0' . Now, i think cgminer involved? I can share dump only after weeked.
Sincerly, I think it is a cgminer issue, but I will take a look at your dump if you want.
After some more playng with this cgminer I came to the conclusion: he work fine on 1024x difficulties, e.g. 1024, 2048, 4096 etc. Maybe 256, 512 too. If pool set other digits, cgminer assume it as 0.
OK, closing the bug.
Thank you for the feedback.
When trying connect cgminer 4.9.1+ (kanoi) to proxy got message like Pool 0 set difficulty 0 as a result all hashpower rejected by pool. proxy pointing to antpool or bitcoindigger - same results. when i using slush0 proxy - all working fine on both pools.