Upcoming downtime

Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Upcoming downtime

by Steve Sokolowski · · Post #24574

On the afternoon of August 1, there will be about 30 minutes of downtime. A redesign of the website will be released, along with two additional new features that will debut for Awesome August. The release candidate for the website (which does not include the two new feature) is available at https://test.prohashing.com/ already, and you can use it right now.

These new features, which will allow us to take on the biggest pools in the world, require major database changes and it could take some time for the updates to every past share to be written to the disks. The exact timing of the release will be provided earlier that day, and will most likely be in the afternoon EDT.

All services will be offline during this period except for the forums and the support ticket system. Please refrain from submitting support tickets about the system being offline. Updates will be provided on the forums.

Because the changes are so massive, we will not be able to revert in the case that a bug comes out that wasn't identified in testing. Therefore, once released, we will work on any issues that arise instead of reverting unless the problem is so dramatic that a 12-hour restore from backup is the only option.
Last edited Thu Jul 25, 2019 07:50 PM UTC by Steve Sokolowski; edited 1 time(s).
Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: Upcoming downtime

by Steve Sokolowski · · Post #24590

ryguy wrote: The mining server isn't down, but live data is. I'm not sure that this post is related to the present issue.
That was a different issue. Chris upgraded the live updates server, and installed Crossbar with a different filename. The program that checks whether the live server was down or not didn't detect the crash because Chris forgot to change the filename in our failsafe program, so he didn't know the live server had crashed.

This error won't happen again, because we fixed both the problem that caused the crash, and also the monitoring program.