Miner is sending shares to to frequently, is therefore being ignore

I get an error on one of my miners under the live worker status and the error says, Miner is sending shares to to frequently, is therefore being ignore its from nicehash and its @ 10ghash and nicehash rental reports shows good mining.. am I being rob 10ghash of my mining????


Last 5 minutes
2017-07-20 19:24:58 - 2017-07-20 19:29:58
For selected chart's time span
2017-07-20 19:09:58 - 2017-07-20 19:29:58
Speed at pool 11.8541 GH /s 12.0050 GH /s
Speed paying 10.3450 GH /s 11.7761 GH /s
Delta +1.5091 GH /s (+12.73%) +0.2289 GH /s (+1.91%)
Rejected at pool 0.0573 GH /s (0.48%) 0.0335 GH /s (0.28%)
Extra rewards 0.0322 GH /s 0.0703 GH /s
Timed-out speed 0.0000 GH /s 0.0000 GH /s

eb7b5b0e-e3be-49ac-9140-8053415d4ac6Scrypt 00:09
BitConnectcoin 3.73 GH/s BitConnectcoin

fc212a7b-fd20-4857-a947-31aae95c77f7Scrypt 00:22
Gulden 9.92 GH/s (1 error) Gulden

Pool Status Miners Speed GH /s Current diff
192.3.198.21:3333 OK. 24 6.3296 524288.00000000
192.3.198.21:3333 OK. 10 4.3074 131072.00000000
Total 34 10.6370

Hey sirslayerjr, by using the d= password parameter, you're setting a static difficulty. The error is saying that difficulty is too low and it is going to ignore that password parameter and instead use a higher difficulty. This shouldn't effect your earnings.

If your worker is submitting more than 1 share per second on average, then you will get that error and will be reverted to automatic difficulty. You need to use a higher static difficulty.

ive been using d=131072 for 6 months.. i need to up it ??

If you're using that high of a difficulty, then you have an amazing amount of hashpower on one connection.

How often do you think your miners were submitting shares? Was it more than twice per second?

its from a nicehash rental.. never had an issue for the last 6 months till now. idk if it was twice per second from nice hash..?? still i only got a fraction of my submitted shares

i believe I now have this same issue. Stopped mining from NH earlier today because the numbers just weren't adding up as they have been over past couple months.

Is this related to the automatic increase in diff? Seems to be the major change I can think of since this has occurred and I've seen my diff climb up to 512k on 5 or 10gh rental

We hope to eliminate this error in the coming days after we make changes to allow the system to handle more shares. The major problem right now is that when errors occur, we lose as many as four hours of development time correcting balances and handling customer support tickets. But we're making progress, and with the weekend arriving, we hope to get further this weekend.