Author

Topic: stratum from pool 0 requested work restart (showing up 5+ in a row) (Read 1439 times)

legendary
Activity: 1302
Merit: 1068
a week ago got a couple of antminer u3's (brand new) running them using cgminer 4.9.2. Hashing went well the first week, now
get the line "stratum from pool 0 requested work restart" atleast 5+ times in a row, then maybe a few accepted and then back to "stratum from pool 0 requested work restart"

this happens for atleast 10 mins, and then the whole thing just repeats "stratum from pool 0 requested work restart", till I shut it down.

Its driving me crazy...the hashrate is pretty decent, getting atleast 50 - 60 ghs average per U3 (which is pretty much what it was rated to run at)

check on the net, mostly see comments stating that its a "normal message which appears when the bitcoin chain finds a block as a whole" and "message usually appears on a p2pool"

I understand that part, but 5+ times in a row, seems kinda messed and I was mining on Slush's Pool, plus a few other sha256 coins, but same thing keeps happening

Right now just boxed them away...want to get right back into hashing  Cry any tips?


It doesnt really affect your hashrate, so i'm not sure why you are fixating on this issue. Regardless, what was your pool side hashrate and also what difficulty did you run them at?
hero member
Activity: 668
Merit: 500
a week ago got a couple of antminer u3's (brand new) running them using cgminer 4.9.2. Hashing went well the first week, now
get the line "stratum from pool 0 requested work restart" atleast 5+ times in a row, then maybe a few accepted and then back to "stratum from pool 0 requested work restart"

this happens for atleast 10 mins, and then the whole thing just repeats "stratum from pool 0 requested work restart", till I shut it down.

Its driving me crazy...the hashrate is pretty decent, getting atleast 50 - 60 ghs average per U3 (which is pretty much what it was rated to run at)

check on the net, mostly see comments stating that its a "normal message which appears when the bitcoin chain finds a block as a whole" and "message usually appears on a p2pool"

I understand that part, but 5+ times in a row, seems kinda messed and I was mining on Slush's Pool, plus a few other sha256 coins, but same thing keeps happening

Right now just boxed them away...want to get right back into hashing  Cry any tips?
Jump to: