Today, I determined that some shares were being lost due to WAMP overload. I addressed the problem in multiple ways: first, shares were lost upon disconnect due to a misunderstanding of how Autobahn behaved, so I prevented them from being lost in the case of a disconnect. Second, I reduced the number of disconnects in the first place by inserting more shares at once. Third, I resolved a memory leak that would cause the system to become unstable about 6 hours after repeated disconnects.
Now that these issues are resolved, it seems that miners are making 1.02 times what they should earn. I'll leave that to run as is and try to figure out where the math is wrong after all corrections are issued.
While I'm confident that major balance issues have been resolved at this point, there are still balance corrections to be made for today. There are also a few miners that need to have their accounts investigated for August 7-9. Chris will evaluate all balance corrections as a whole when he returns from Canada on Wednesday and will adjust for everything at once for the entire week.
We won't be able to relax the difficulty constraints today. While I had hoped that coin assignment was the next bottleneck, it turns out that WAMP traffic has soared and WAMP parallelism is the next issue that needs to be addressed. That should be much simpler than what we did with share insertion, but I'm not willing to release that until it's tested later in the week.
I've gotten the queue down to 29 tickets and 11 private messages. The tickets take priority, and I plan to try to get them all closed or to "awaiting customer reply" status by tonight. I'll reply to private messages later in the week. If you notice that something is still wrong, feel free to reply or submit a ticket.
Thanks for your patience during this trying time!
Note: there appears to be some sort of connectivity issue, which I think is caused by Javapipe's DDoS protection. We will switch to Comcast Enterprise if we decide on the "invest a lot" option, so those problems should go away in that case.
Update on recent issues
Forum rules
The News forum is only for updates about the Prohashing pool.
Replies to posts in this forum should be related to the news being announced. If you need support on another issue, please post in the forum related to that topic or seek one of the official support options listed in the top right corner of the forums page or on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
The News forum is only for updates about the Prohashing pool.
Replies to posts in this forum should be related to the news being announced. If you need support on another issue, please post in the forum related to that topic or seek one of the official support options listed in the top right corner of the forums page or on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
- Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Update on recent issues
Last edited by Steve Sokolowski on Sun Aug 13, 2017 6:48 pm, edited 1 time in total.
Re: Update on recent issues
Would appreciate checking my earnings history aswell, im not going to make a ticket about it, mostly it seem to have been corrected, and i much appreciate the way you run this pool, and i plan to stick around.
Running rigs: KNC Titan, Antminer D3 & L3+'s
-
- Posts: 25
- Joined: Tue Aug 08, 2017 3:08 pm
Re: Update on recent issues
Thank you Steve, all working good as of 650pm EST
Re: Update on recent issues
Was there an issue with payments not being sent out Sunday? Because my LTC payment for the 12th never came.
-
- Posts: 646
- Joined: Sun Apr 16, 2017 3:01 pm
Re: Update on recent issues
there is a known issue with some coins not paying out. the team are aware of the issue and are working on it