Database got behind earlier
Posted: Thu Jun 14, 2018 7:21 pm
The database got behind earlier today, but is catching up. The hashrate charts will adjust upward after all the shares are inserted.
We're still trying to figure out what happens to the system around 1:00 or 3:00pm EDT periodically, and this has stopped all our progress on mining server improvements over the past two weeks. The WAMP server seems to have connectivity issues, which somehow causes the primary mining server to disconnect. Then, the latest block data isn't received from the server, causing stale shares, and it needs to be restarted. The connectivity issues also cause "undefined" workers to be sent out to customers across the miner updates channels. We are wondering whether this issue is related to the problem of scrypt hashrate being reported too high at the top of the forums.
Fortunately, the share inserters are stable and have prevented losses of shares, but we're still trying to figure out how we can diagnose these connectivity issues. There's nothing in the WAMP logs to indicate a reason for the disconnects. We'll continue trying over the weekend, and this will continue to be the #1 issue to resolve.
We're still trying to figure out what happens to the system around 1:00 or 3:00pm EDT periodically, and this has stopped all our progress on mining server improvements over the past two weeks. The WAMP server seems to have connectivity issues, which somehow causes the primary mining server to disconnect. Then, the latest block data isn't received from the server, causing stale shares, and it needs to be restarted. The connectivity issues also cause "undefined" workers to be sent out to customers across the miner updates channels. We are wondering whether this issue is related to the problem of scrypt hashrate being reported too high at the top of the forums.
Fortunately, the share inserters are stable and have prevented losses of shares, but we're still trying to figure out how we can diagnose these connectivity issues. There's nothing in the WAMP logs to indicate a reason for the disconnects. We'll continue trying over the weekend, and this will continue to be the #1 issue to resolve.