p2pool error "submitted share with hash > target"

[diefatty]

I've been mining with p2pool for a few weeks now, but recently I've been getting this error: "..submitted share with hash > target:"

What does this mean and how do I solve it?

[1714978070]

1714978070

[1714978070]

1714978070

[1714978070]

1714978070

[CohibAA]

bump

 

[Kluge]

Basically, your miner is sending shares to p2pool which aren't "good enough." It doesn't meet the requirement p2pool set, so p2pool is rejecting the shares, but your mining client is still sending them, apparently ignoring what p2pool is saying is the threshold for a "good enough" share.

Latency issue, I'd guess, or misconfigured mining client.

From p2pool FAQ:
Q: Why do I get lots of "Worker <name> submitted share with hash > target:" in my P2Pool logs? It seems to put a large CPU load on P2Pool.
A: Your miner may not support pool-settable difficulties. It may be a problem if the rate of these messages gets very high (putting more strain on p2pool). Using stratum-proxy or the scrypt version might help.

[CohibAA]

Thank you for the quick reply.  

My rate of these messages for my miner is not very often, especially compared to some of the miners I've seen connected to my node.  My reject rate is around 1% on average per the p2pool node stats (Litecoin scrypt node), but I was not sure if their was something else I could do to reduce the rate.  I think I run a pretty decent p2pool config, but I am always looking to learn and improve.