distributed.net staff keep (relatively) up-to-date logs of their activities in .plan files. These were traditionally available via finger, but we've put them on the web for easier consumption.
We experienced some hardware issues with our keymaster server today, possibly due to a mechanical issue. It had a few hours of downtime on 2015-05-16 causing work to become backlogged and buffered on our keyserver network, which means that the stats for that day will be significantly lower than usual, however tomorrow’s stats should include all of that backlogged work. Newly submitted work is continuing to be processed without delay at this point.
Although the keymaster is back online for the moment, we are continuing to do remote hardware diagnostics. It sounds likely that we may need to replace a system case fan however. Thanks for your patience and support!
We’re currently in the process of doing some backend database, webserver, and OS upgrades to our stats servers, so we’ve temporarily disabled access to it until we’re done. Once we’ve verified that everything appears to be working, we’ll brings the stats pages back online. No project data will be lost during this maintenance, and we’ll restart stats processing once it’s done. Thanks for your patience.
Update: This maintenance has now been completed and everything is back to normal.
two rackmount servers, one rackmount UPS, and two dozen donuts being transported to a new home
standard and deviation, before the move
As previously announced, we had to move our stats servers to a new hosting location due to changes at our old hosting provider. Logistically it was quickest and easiest for us to simply physically move the two servers to their new location in Houston, so we completed that move today. Zone file entries have been updated, so http://stats.distributed.net/ should now take you to the new location once any cached DNS entries have been propagated.
The downtime was a little longer than planned because of an unexpected routing failure that began at our old location earlier than our planned start of the move. We also waited until stats has fully processed all of its backlog before officially publicizing its new IP address at its new location.
Part of the transport occurred by private plane, and although the outbound flight was tracked on FlightAware, the return flight was unfortunately not publicly visible due to an air traffic control limitation.
No dnetc work submitted during the downtime was lost, and our stats pages should now fully reflect the last day of work.
Our stats server is currently offline as we prepare it for relocation. We expect it to be back online tomorrow around 2014-05-11 at about 22:00 UTC but it is possible that we may need to delay its restart time.
During the downtime we will be physically relocating our servers 160 miles, from Austin, TX to a new hosting location in Houston, TX offered by FlightAware. Part of the transport will be conducted by private plane, which might be visible on the FlightAware flight tracking website around 2014-05-11 at 17:00 UTC.
We’d like to thank Midas Green Tech in Austin, TX for the use of their hosting facilities over the years, but their business is transitioning away from physical hosting and towards virtual hosting so our move was an unfortunate necessity. If you are in need of any cloud hosted services, we encourage you to check out their offerings and mention that you heard about them from distributed.net
As always, all dnetc work transmitted during the downtime will be fully counted once our stats website is brought back online.
We’ve taken statsbox temporarily offline for some minor system updates. It should be back online before the next statsrun. As usual, there will be no impact to stats or our proxy network during this downtime.
UPDATE: It is back online now and no problems were encountered during the maintenance.
edit: stats now back up, thanks for your patience!
Stats is currently down due to technical difficulties – engineers are working to bring the system back online as soon as possible.
As always, no work will be lost while the site is down – all submitted blocks will be credited as normal.
The statsbox is offline at the moment. We’re hoping to get it back online tomorrow. As always, no credit will be lost while it is inaccessible. We’ll update this post with more details later. Thanks!
UPDATE: stats is back online and caught up. Thanks for your patience!
After several weeks of anticipation, we’ve finished deploying our new stats servers and have fully transferred operations to them. The two new machines (standard and deviation) should be able to provide us with sufficient capacity and reliability for the foreseeable future. You can check out a picture of standard and deviation in our photo gallery. Full hardware specs on our current and past servers are also listed on the statsbox FAQ page. Our old server, fritz, has been physically relocated offsite and is awaiting a disk wipe before we decide its final fate.
Stats should again be available at http://stats.distributed.net/ No loss of data occurred during this server transition.
We’d also like to thank Midas Networks in Austin, Texas for continuing to provide excellent hosting services to us.
Thanks for your attention!
We’ve taken our stats server temporarily offline while we do the final cut-over to our new server hardware. If all goes well, the upgrade should be complete in time for today’s statsrun.
We’ve temporarily put our stats server into “read-only” mode, which means that you’ll be able to view your current stats (and they will continue to be updated daily) but you won’t be able to make any changes to your user account or team. As usual, no client work will be affected during this period.
This is being done to prepare for switchover to new hardware that will replace our aging stats server some time next week. Read-only mode allows us to make and restore database backups without losing any user-made edits. We’ll make another announcement once the new hardware is fully deployed.
If you’re curious, some details about the new stats hardware are listed on our FAQ page.