slush0 / stratum-mining-proxy

Application providing bridge between old HTTP/getwork protocol and Stratum mining protocol.
400 stars 280 forks source link

REJECTED at 100% with latest build. #35

Closed TazMan143 closed 10 years ago

TazMan143 commented 11 years ago

I had been running your older build from August with no issues. Since moving to the latest build I get the following. I have tried with both the stratum and getwork protocols.

./mining_proxy.py -o stratum.ltc123.net -p 3333 2013-10-04 07:54:54,889 INFO proxy jobs. # C extension for midstate not available. Using default implementation instead. 2013-10-04 07:54:54,907 WARNING proxy mining_proxy.main # Stratum proxy version: 1.5.2 2013-10-04 07:54:54,915 WARNING proxy mining_proxy.test_update # Checking for updates... 2013-10-04 07:54:56,079 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at stratum.ltc123.net:3333 2013-10-04 07:54:56,204 INFO stats stats.print_stats # 1 peers connected, state changed 1 times 2013-10-04 07:54:56,204 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at stratum.ltc123.net:3333 2013-10-04 07:54:56,205 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs 2013-10-04 07:54:56,333 WARNING proxy mining_proxy.main # ----------------------------------------------------------------------- 2013-10-04 07:54:56,333 WARNING proxy mining_proxy.main # PROXY IS LISTENING ON ALL IPs ON PORT 3333 (stratum) AND 8332 (getwork) 2013-10-04 07:54:56,333 WARNING proxy mining_proxy.main # ----------------------------------------------------------------------- 2013-10-04 07:54:56,334 INFO proxy client_service.handle_event # Setting new difficulty: 128 2013-10-04 07:54:56,334 INFO proxy client_service.handle_event # New job 3d98 for prevhash 2e62b5d8, clean_jobs=True 2013-10-04 07:55:11,069 INFO proxy client_service.handle_event # New job 3d99 for prevhash 2e62b5d8, clean_jobs=False 2013-10-04 07:55:36,429 INFO proxy client_service.handle_event # New job 3d9a for prevhash d029c168, clean_jobs=True 2013-10-04 07:55:57,328 INFO stats stats.print_stats # 2 peers connected, state changed 1 times 2013-10-04 07:56:11,011 INFO proxy stratum_listener.submit # [123ms] Share from 'TazMan143.gpu1' REJECTED: (-2, u'Share is above target', None) 2013-10-04 07:56:12,493 INFO proxy stratum_listener.submit # [124ms] Share from 'TazMan143.gpu1' REJECTED: (-2, u'Share is above target', None) 2013-10-04 07:56:15,516 INFO proxy stratum_listener.submit # [122ms] Share from 'TazMan143.gpu1' REJECTED: (-2, u'Share is above target', None) 2013-10-04 07:56:16,971 INFO proxy stratum_listener.submit # [123ms] Share from 'TazMan143.gpu1' REJECTED: (-2, u'Share is above target', None) 2013-10-04 07:56:18,461 INFO proxy stratum_listener.submit # [123ms] Share from 'TazMan143.gpu1' REJECTED: (-2, u'Share is above target', None) 2013-10-04 07:56:18,501 INFO proxy stratum_listener.submit # [124ms] Share from 'TazMan143.gpu1' REJECTED: (-2, u'Share is above target', None) 2013-10-04 07:56:21,542 INFO proxy stratum_listener.submit # [124ms] Share from 'TazMan143.gpu1' REJECTED: (-2, u'Share is above target', None) 2013-10-04 07:56:21,542 INFO proxy stratum_listener.submit # [124ms] Share from 'TazMan143.gpu1' REJECTED: (-2, u'Share is above target', None) ^C2013-10-04 07:56:23,585 INFO proxy mining_proxy.on_shutdown # Shutting down proxy... 2013-10-04 07:56:23,586 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at stratum.ltc123.net:3333 2013-10-04 07:56:23,586 INFO stats stats.print_stats # 1 peers connected, state changed 1 times 2013-10-04 07:56:23,587 INFO stats stats.print_stats # 0 peers connected, state changed 1 times

RoostayFish commented 10 years ago

Awesome, ive been trying too but this really isnt my area and i dont know python much.

Just thought i would make some suggestions to point people in the right direction :+1:

derenma commented 10 years ago

hey... i am getting nothing but accepted blocks with sgminer using the new version of stratum. :)

On Mon, Jan 27, 2014 at 9:15 AM, RoostayFish notifications@github.comwrote:

Awesome, ive been trying too but this really isnt my area and i dont know python much.

Just thought i would make some suggestions to point people in the right direction [image: :+1:]

— Reply to this email directly or view it on GitHubhttps://github.com/slush0/stratum-mining-proxy/issues/35#issuecomment-33370550 .

RoostayFish commented 10 years ago

Oh really... Ill have to try again shortly.

derenma commented 10 years ago

aye... i am re-pulling the proxy from git to ensure that i am not using the proxy with my mods.

On Mon, Jan 27, 2014 at 9:27 AM, RoostayFish notifications@github.comwrote:

Oh really... Ill have to try again shortly.

— Reply to this email directly or view it on GitHubhttps://github.com/slush0/stratum-mining-proxy/issues/35#issuecomment-33371442 .

derenma commented 10 years ago

sgminer it is. :) its working great for my miners.

On Mon, Jan 27, 2014 at 9:33 AM, M. Deren matthew.deren@gmail.com wrote:

aye... i am re-pulling the proxy from git to ensure that i am not using the proxy with my mods.

On Mon, Jan 27, 2014 at 9:27 AM, RoostayFish notifications@github.comwrote:

Oh really... Ill have to try again shortly.

— Reply to this email directly or view it on GitHubhttps://github.com/slush0/stratum-mining-proxy/issues/35#issuecomment-33371442 .

RoostayFish commented 10 years ago

Hmm my 2nd miner is getting 100% rejects "INFO proxy stratum_listener.submit # [311ms] Share from 'RoostayFish.2' REJECTED: (-2, u"Job '6200' not found", None)"

liling commented 10 years ago

If all your miner use same username, sgminer works fine with stratum proxy, but if your miner use different username, rejected happens.

Another problem is if all your rig use just one username, mining pool (MPOS based PPLNS) consider you has a very big rig and would adjust your difficulty to a very high value, this make small rigs rarely submit share.

slush0 commented 10 years ago

but if your miner use different username, rejected happens.

Does this happen only with sgminer or is this general bug?

consider you has a very big rig and would adjust your difficulty to a very high value, this make small rigs rarely submit share.

This is a feature, not a bug. Your hashrate is same if you have 100 miners with 1 MHash or one miner with 100 MHash; by using stratum proxy, group of smaller miners act as one big miner, so the difficulty adjust, but the total accepted share ratio is still the same...

p4u commented 10 years ago

sgminer works perfect!

Slush0, I'm trying to execute the stratum proxy with options: -cu myworker -cp mypass But in the pool page the worker which sends the shares is not "myworker" but the worker configured in the sgminer. So the stratum proxy is not changing the worker/pass of the packets send to the pool. Am I using wrong this feature? Sorry for asking, but I cannot find the documentation about that.

slush0 commented 10 years ago

p4u: --custom-user has been originally designed only for getwork interface (in fact I designed this for my own purpose where I needed only getwork API to work). Now I implemented it also for stratum. I don't have miner here so I didn't have a chance to test it deeply. Please try latest git and let me know if it works.

slush0 commented 10 years ago

Can I close this issue? It seems to be resolved already (the problem wasn't in proxy, but in some versions of cgminer) and sgminer seems to work for all of you...

liling commented 10 years ago

I tested minerd and it works fine with different usernames

slush0 commented 10 years ago

Yay, /me is the coding ninja

RoostayFish commented 10 years ago

So the problem with multiple rigs mining with different users is a different issue that i could report?

p4u commented 10 years ago

Slush0, it works perfect. Now it is possible to use -cu -cp with stratum servers too. Thank you!

p4u commented 10 years ago

I think you can close the ISSUE

slush0 commented 10 years ago

RoostayFish - yes, it was different issue, but yesterday I fixed both of them.

RoostayFish commented 10 years ago

I still can only connect with one username. If i use 2 i get rejects.

./mining_proxy.py -o pool -p 3339 -sp 3333 -nm -st -v

Please advise if i should post here or somewhere else.

bmoconno commented 10 years ago

I'm having this issue and can't find if anyone found a workable solution for multiple machines using the same proxy?

To re-iterate, for versions of cgminer after 3.2 all shares are rejected when using slush0's stratum proxy. Version 3.2 and below all work perfectly. So I have to believe it's still the 2 byte vs 4 byte nonce issue mentioned here.

I've read through the commits for p4u's fork after January and nothing seems to mention this problem or it being solved.

Thanks!

p4u commented 10 years ago

It is not solved and I don't think it will be solved since it is a cgminer problem.

mdude77 commented 10 years ago

On 5/17/2014 5:06 PM, Pau wrote:

It is not solved and I don't think it will be solved since it is a cgminer problem.


Reply to this email directly or view it on GitHub https://github.com/slush0/stratum-mining-proxy/issues/35#issuecomment-43424109.

Use sgminer. it works fine with the proxy.

M