Pricing update failed again

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.
Locked
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Pricing update failed again

Post by Steve Sokolowski » Mon May 14, 2018 11:27 am

It looks like the price updater software hung again, and the mining server stopped mining due to the same failsafe that was triggered last week. For those who forget, the problem was that WAMP disconnected the price updating software at the same time the prices were being sent to the mining server. This bug has already been fixed, but the release had not yet been issued.

Chris restarted the price updater and the issue is temporarily resolved. We're not sure why this issue occurred twice in the past four days after not having happened for four years before, but once the fix is deployed later today, it shouldn't happen again.

We apologize for the issue.
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Pricing update failed again

Post by Steve Sokolowski » Mon May 14, 2018 11:34 am

To update this post, there was a miscommunication. The code was already released, and the system worked as designed, successfully retrying after being disconnected. However, for an unknown reason, the price updater still can't connect to the WAMP server.

We're investigating the issue and will update everyone shortly.
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Pricing update failed again

Post by Steve Sokolowski » Mon May 14, 2018 11:46 am

Chris figured out the problem. The code works as designed, but when it was deployed, the IP address of the development WAMP server was not changed to the IP address of the production WAMP server. Chris updated the IP address and the issue has been resolved.
Locked