All of a sudden the reject share rate went up rapidly...

[Steve Sokolowski]

Hello again... anyone else notice their rigs running ETHash getting all shares rejected as of 15 minutes ago or so? All three are in the reds. I’ve also tried updating and rebooting to no avail. Hope this is all temporarily. Thanks!

We are aware of this issue and are currently investigating. It likely has something to do with the new ETH network clients that were released today to prepare for the Merge.

Copy that. Thanks, Steve!

We resolved the issue successfully. Because it's so late, I'll report exactly what happened tomorrow. Mining is back online, and sorry for the inconvenience!

[DeafEyeJedi]

We are aware of this issue and are currently investigating. It likely has something to do with the new ETH network clients that were released today to prepare for the Merge.

Copy that. Thanks, Steve!

We resolved the issue successfully. Because it's so late, I'll report exactly what happened tomorrow. Mining is back online, and sorry for the inconvenience!

Thanks so much, Steve! Looking forward to your initial report tomorrow. Happy Mining!

[Steve Sokolowski]

Copy that. Thanks, Steve!

We resolved the issue successfully. Because it's so late, I'll report exactly what happened tomorrow. Mining is back online, and sorry for the inconvenience!

Thanks so much, Steve! Looking forward to your initial report tomorrow. Happy Mining!

Thanks for your patience.

We discovered that the geth developers removed a field in their API calls that allow pools to determine how many are in, and how much value there is, of transactions in the next block. The removal of the field caused our daemon management software to fail to send new block notifications to the mining servers.

After some time, Vance restarted the mining servers to prepare for Autolykos2's release. At that point, because no blocks were being received from ethash daemons, the coins went into error because their DAGs couldn't be computed. The DAGs couldn't be computed because it wasn't known which block to compute the DAG for.

That issue was resolved quickly, but an additional problem was discovered that required an hour to troubleshoot. There was a bug in the daemon managers where, when a coin's host was changed (as Steven did when he reverted to the previous version of geth,) the new server's daemon manager would not retrieve the data from the database and therefore would not be aware that the coin had been moved to that server. Restarting the daemon managers on all servers resolved that issue.

I added a ticket and assigned to Vance that, before the end of the month, he will deploy a fix to the daemon managers so that, in the rare case that a coin is moved between servers, the daemon managers will now refresh from the database the new coin locations and respond accordingly without needing to be restarted.

[DeafEyeJedi]

We resolved the issue successfully. Because it's so late, I'll report exactly what happened tomorrow. Mining is back online, and sorry for the inconvenience!

Thanks so much, Steve! Looking forward to your initial report tomorrow. Happy Mining!

Thanks for your patience.

We discovered that the geth developers removed a field in their API calls that allow pools to determine how many are in, and how much value there is, of transactions in the next block. The removal of the field caused our daemon management software to fail to send new block notifications to the mining servers.

After some time, Vance restarted the mining servers to prepare for Autolykos2's release. At that point, because no blocks were being received from ethash daemons, the coins went into error because their DAGs couldn't be computed. The DAGs couldn't be computed because it wasn't known which block to compute the DAG for.

That issue was resolved quickly, but an additional problem was discovered that required an hour to troubleshoot. There was a bug in the daemon managers where, when a coin's host was changed (as Steven did when he reverted to the previous version of geth,) the new server's daemon manager would not retrieve the data from the database and therefore would not be aware that the coin had been moved to that server. Restarting the daemon managers on all servers resolved that issue.

I added a ticket and assigned to Vance that, before the end of the month, he will deploy a fix to the daemon managers so that, in the rare case that a coin is moved between servers, the daemon managers will now refresh from the database the new coin locations and respond accordingly without needing to be restarted.

Fantastic updates. Good to hear. I appreciate the follow up, Steve!

[yotiy]

The "GPU Ethash Static Diff Issue" refers to a problem encountered by GPUs while mining cryptocurrencies using the Ethash algorithm. This issue can cause fluctuations in mining difficulty, affecting mining efficiency and profitability. Miners experiencing this problem may need to adjust their mining settings or seek assistance from technical support.

For those in South Africa, looking to Where To Buy Xanax UK, ensure to explore reputable online pharmacies and consult with a healthcare professional before making any purchase.

[garagedoorhighl]

It sounds like there's been a sudden increase in the reject share rate, which could be concerning. A spike in reject shares might indicate issues with your mining hardware, network Car with driver in dubai connectivity, or the mining pool itself.