Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stratum keeps requesting work restart #95

Closed
colt05 opened this issue Nov 29, 2015 · 6 comments

Comments

@ghost
Copy link

@ghost ghost commented Nov 29, 2015

Hey guys, I have been mining for bitcoins on Slush's Pool (stratum+tcp://stratum.bitcoin.cz:3333) and cpuminer is running on a Koding VM. I keep getting "Stratum requested work restart" but then I get this:
thread 0: 257818480 hashes, 8591 khash/s
DEBUG: hash > target (false positive)
Hash: 0000000050ea2b0ac608b30d08178e7b13d21e13a47f12d6ebd6a253466ef777
Target: 000000001fffe000000000000000000000000000000000000000000000000000
DEBUG: hash > target (false positive)
Hash: 00000000484c19edc82403e1a83b785ddb210c653f4d00e8b05336a370960acf
Target: 000000001fffe000000000000000000000000000000000000000000000000000
I never got this far on TomPool multipool (I am using Slush's pool now though which tells me my worker is offline), so is there a fix for the work restart? Thanks.

@pooler

This comment has been minimized.

Copy link
Owner

@pooler pooler commented Nov 29, 2015

A few work restarts per minute are totally normal. Besides, it's the server that decides when the client should start working on a new job, and there's nothing you can do about that.
False positives are also totally normal when the share difficulty is higher than 1. (Your examples show a difficulty of 8).

@ghost

This comment has been minimized.

Copy link
Author

@ghost ghost commented Nov 30, 2015

Thanks! But sometimes, it says "Stratum requested work restart" after every time it says something like "thread 0: 257818480 hashes, 8591 khash/s."

@pooler

This comment has been minimized.

Copy link
Owner

@pooler pooler commented Nov 30, 2015

That is also normal. When switching jobs the number of computed hashes and the speed are printed (unless quiet mode is enabled).

@ghost

This comment has been minimized.

Copy link
Author

@ghost ghost commented Nov 30, 2015

Oh, is that so? Thanks for the information.

@colt05 colt05 closed this Nov 30, 2015
@reppolice

This comment has been minimized.

Copy link

@reppolice reppolice commented May 7, 2017

Hmm, doesn't that "switching jobs" mean the work has been lost, since only "shares yay" count?

@pooler

This comment has been minimized.

Copy link
Owner

@pooler pooler commented May 8, 2017

@reppolice No, it doesn't. Mining is a memoryless process, there is no "progress" that you can lose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.