SourceForge Infrastructure and Service Restoration update for 7/31

On 7/16, Slashdot Media sites (including Slashdot and SourceForge) experienced a storage fault. Work has continued 24×7 on service restoration. Updates have been provided as each key service component was restored. We’ve provided four prior updates (7/18, 7/22, 7/24, 7/28) summarizing our infrastructure and service restoration status. This is our fifth and final large update for this incident.

As of 7/31, all Slashdot Media sites and services have been restored.

Activity since our 7/28 full update:

  • SourceForge file upload capability was restored to service on 7/31, matching our announced ETA.
  • SourceForge CVS service, non-Allura-backed Bazaar (bzr) SCM service, and interactive shell service were restored on 7/31, ahead of our announced ETA.

SourceForge staff will continue to monitor and respond to the support ticket queue.  If you are in need of support, please submit a ticket at: https://sourceforge.net/p/forge/site-support/new/

Root cause analysis (RCA) for this incident has been formed.  Slashdot Media teams will continue to meet next week to complete preparation of recommendations and post-mortem documentation.  Additional information to be provided to the community via this blog.

Thank you for your continued support and patience.

8 Responses to “SourceForge Infrastructure and Service Restoration update for 7/31”

  1. Emmanuel Puybaret Aug 1, 2015 at 10:48 am #

    Thanks for the hard work. I could commit the pending source code of Sweet Home 3D and upload the files of version 5.0 with no problem. Have a nice rest!

    • rgaloppini Aug 1, 2015 at 1:42 pm #

      Hi Emmanuel, I’m glad you appreciated, and it is good to ear everything works fine for you now!

  2. Gonzalo Garramuño Aug 3, 2015 at 1:59 pm #

    Thanks for all the hard work. It was a difficult one this time around.

  3. Cameron Aug 3, 2015 at 10:36 pm #

    Thank you for your hard work! This incident has been last for about one month. I am waiting for a root cause analysis post for this incident. I think it should be an important learning example in internet history.

  4. RyanJose Aug 5, 2015 at 3:19 am #

    To avoid any risk when downloading FileZilla, we recommend that you only download FileZilla from the official FileZilla website or from.

  5. Matthieu Aug 5, 2015 at 4:03 am #

    Thanks but the download/upload is still completely screwed up. Impossible to add or remove a file or folder, the last uploaded files are not available. I guess that’s why the company is being sold.

    • Matthieu Aug 5, 2015 at 4:13 am #

      Managed to delete the corrupted files, still a pain.

  6. DMcCunney Aug 5, 2015 at 6:48 pm #

    The part I really want to see is the root cause analysis. When I saw the outage reports, my first question was what sort of file system corruption could have caused the reported problems, and how that corruption could have occurred. I assume the SourceForge team is working hard to find the answers to both questions, and make sure that sort of failure can’t happen *again*. I look forward to hearing all about it when you have the answers. ______ Dennis