"no valid shares" on most of my L3+

I have also been getting "no valid shares" for a few hours on couple of my L3s. Prohashing pool is showing dead and alive. However, two others are working fine. They all have d=131072.

Now the others also have "no valid shares"! Oh well I go NH for now.

Steve Sokolowski wrote:

alvarezgen wrote:

Steve Sokolowski wrote:
Unfortunately, we've been working on this issue for a month and still don't have any leads. Chris is going to try increasing the rejected share ban threshold today on the theory that because L3s have so much hashrate, they are more likely to submit rejected shares and exceed the ban threshold.

Hopefully, that will make a difference.

Same problem here on all my L3+. I have been mining with no problem for the past 2 - 3 days, but since yesterday I'm getting "no valid shares".

I hope increasing the rejected share ban threshold can fix this.

We just increased the threshold. Have you had more success now?

I have been mining for a couple of hours with no problem so far. I'll let you guys know if any eventuality

alvarezgen wrote:

Steve Sokolowski wrote:

alvarezgen wrote:
Same problem here on all my L3+. I have been mining with no problem for the past 2 - 3 days, but since yesterday I'm getting "no valid shares".

I hope increasing the rejected share ban threshold can fix this.

We just increased the threshold. Have you had more success now?

I have been mining for a couple of hours with no problem so far. I'll let you guys know if any eventuality

That's great to hear. Please submit a support ticket if this problem returns.

Hi Steve...
It was working fine for a while, but I'm getting the issue again...

Thanks!

I noticed the same issue today for the first time as well with my single L3+. Yesterday was my first day and I didn't see this problem. I'm new here, not sure on protocol. Should I submit a ticket?
Edit: I've switched to litecoinpool until I learn more about internal config settings on my ant miner (other than the pw field settings which are nicely documented here). I will be back after I have more info leading to resolution here.

Steve Sokolowski wrote:

alvarezgen wrote:

Steve Sokolowski wrote:
Unfortunately, we've been working on this issue for a month and still don't have any leads. Chris is going to try increasing the rejected share ban threshold today on the theory that because L3s have so much hashrate, they are more likely to submit rejected shares and exceed the ban threshold.

Hopefully, that will make a difference.

Same problem here on all my L3+. I have been mining with no problem for the past 2 - 3 days, but since yesterday I'm getting "no valid shares".

I hope increasing the rejected share ban threshold can fix this.

We just increased the threshold. Have you had more success now?

duplicate post.. please ignore

Steve Sokolowski wrote:

alvarezgen wrote:

Steve Sokolowski wrote:
Unfortunately, we've been working on this issue for a month and still don't have any leads. Chris is going to try increasing the rejected share ban threshold today on the theory that because L3s have so much hashrate, they are more likely to submit rejected shares and exceed the ban threshold.

Hopefully, that will make a difference.

Same problem here on all my L3+. I have been mining with no problem for the past 2 - 3 days, but since yesterday I'm getting "no valid shares".

I hope increasing the rejected share ban threshold can fix this.

We just increased the threshold. Have you had more success now?

Hello,

I have not noticed big improvement. Can you confirm when it's showing "no valid shares" or "calculating hashrate", are my miners hashing and making money or are they just sitting there?

Thanks.

I switched back to pro hashing today and haven't noticed the issue yet.

I can confirm that the issue is still present. I have 2 of my 5 L3+'s showing no valid shares.
Is there any update?
I will be moving to NH until this is solved
This is what is showing:
Difficulty: 65,536
Target difficulty: 65,536 (dynamic)
Work restart delay: Need more shares
Current restart penalty: 1.000
Minimum network difficulty: Not set
2hr share count: 0
2hr avg hashrate: Need more shares
Since first share: No shares yet
Mode: Pay-per-share
Merge mining restarts: dynamic