Chris restarted server to fix memory error

News updates about the Prohashing pool
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.
Post Reply
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Chris restarted server to fix memory error

Post by Steve Sokolowski » Fri May 12, 2017 8:12 am

Chris restarted the mining server to resolve a memory error. We added the issue to our list of tasks this weekend to investigate. I'm not quite sure what happened, but it appears that at one point there were so many coins being mined that it overflowed the pipe that sends data from the mining server to the process that inserts data into the database.

No money was lost as a result of this error; all that happened was that the shares built up in memory until the server crashed. There is enough data in the database to reconstruct how much is owed to miners for the three hour period earlier today, and Chris will correct balances when he wakes up in 8 hours. As is our policy, a bonus will be paid to today's miners. The correction will use the following calculation: (earnings between 12:00am EDT and tomorrow 12:00am EDT) * ((1440 min per day + 176 min of missing shares) / 1440 min per day) * 1.10 bonus factor. This post will be modified after Chris makes the corrections.

Thanks for your patience, and we should be able to prevent this issue from happening again over the weekend.
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Chris restarted server to fix memory error

Post by Steve Sokolowski » Sat May 13, 2017 8:16 am

Chris corrected all the balances and this issue is now resolved.
Post Reply