Quarterly Maintenance Window (February 21st 2015 from 03:00 AM UTC to 03:00 PM UTC) - COMPLETED

Date / Time: February 21st 2015 from 03:00 AM UTC to 03:00 PM UTC.

Services affected: TeamForge,  few SVN servers , GIT Services.

Description : CollabNet regularly performs system-wide changes to maintain and upgrade common infrastructure components such as power, network, and storage. This is a message to remind you that our scheduled quarterly maintenance window is scheduled on Friday February 20th to update our storage infrastructure and update firewall configurations. 

Impact to Customers: There will be a service interruption of TeamForge and partial SVN services. There will also be some impact on Git commits if integrated with TeamForge service. This task could last up to 12 hrs, We apologize for any inconvenience this may cause.  For more information about this maintenance window, or to report other unrelated issues, please contact CollabNet Support.

Update: Maintenance has been completed.   Please feel free to file support ticket if any issues remain.

Have more questions? Submit a request

26 Comments

  • 0
    Avatar
    Subramanian Vairavan

    Hi All,

    We still have few lingering issues with SVN and TeamForge because of which few customers might face accessing issues and our engineers are working on this and we will keep the post update on the status.

    Thanks,

    Subramanian

    CloudForge Support.

  • 0
    Avatar
    Manuel Dominguez Sarmiento

    We're still getting HTTP 502 Bad Gateway errors:

     

    org.apache.subversion.javahl.ClientException: svn: E175002: Commit failed (details follow):
    svn: E175002: PROPFIND of '/cms/personal-ar/WebContent/WEB-INF/applicationContext-monitor.xml': 502 Bad Gateway (http://renxo.svn.cloudforge.com)
    org.apache.subversion.javahl.ClientException: svn: E175002: Commit failed (details follow):
    svn: E175002: PROPFIND of '/cms/personal-ar/WebContent/WEB-INF/applicationContext-monitor.xml': 502 Bad Gateway (http://renxo.svn.cloudforge.com)

  • 0
    Avatar
    Jonathan Daley

    When trying to commit to my SVN repo, I am getting the following error:

     

    Commit failed (details follow): 
    Commit blocked by pre-commit hook (exit code 1) with output: 
    An internal error occurred:

    LOADING Redis is loading the dataset in memory

    If this problem persists, please contact CloudForge Support 
    at support@cloudforge.com
    This error was generated by a custom hook script on the Subversion server. 
    Please contact your server administrator for help with resolving this issue.

     

    When will this issue be resolved?

  • 0
    Avatar
    Nancy Stronczek

    I am getting the same error as Jonathan Daley.

  • 0
    Avatar
    Chakravarthy Shankar

    Hi All,

     The maintenance is taking longer than the expected time. We are expecting the maintenance to be completed within next six hours. We sincerely apologize for the inconvenience caused due to this. We will update this page right away, once the maintenance is completed.


    Thanks,

    Chakravarthy.

  • 0
    Avatar
    Jonathan Daley

    I have to say I'm quite disappointed by the lack of communication about the maintenance, and how it is going on longer then expected. This has basically made development grind to a halt at my studio today.

  • 0
    Avatar
    Jonathan Daley

    @Nancy Stronczek:  I was just able to do a Commit. Maybe it's working now... worth a try.

  • 0
    Avatar
    Nancy Stronczek

    @Jonathan Daley, thanks for the heads up.  After several more unsuccessful attempts, 2 of my commits finally went through. 

     

    We are releasing this weekend and we have several final fixes that have to go in. This is going to potentially delay our release.  Why does Murphy's Law always prevail?!

  • 0
    Avatar
    Jonathan Daley

    *cross fingers* It's working now. But it's being very slow; the software I use automatically locks files as they're modified, and it's easily taking 5 times longer then normal to apply the locks.

    @Nancy Stronczek, best of luck on your release!

  • 0
    Avatar
    Jason Hill

    Any updates? Commits have been refused for the past three hours for me.

  • 0
    Avatar
    Peter Sørensen

    still commit errors

  • 0
    Avatar
    Jonathan Daley

    Although I had a commit go through a few hours ago, I'm once again not able to post any commits.

    Any updates on when this will be resolved?

  • 0
    Avatar
    Sergio Castineyras

    Quarterly Maintenance Window (February 21st 2014 ...

     

    That was last year then :P

     

    svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:
    An internal error occurred:
        LOADING Redis is loading the dataset in memory

     

     

  • 0
    Avatar
    Jonathan Daley

    I am still unable to commit anything to my repository. I'd like an update on this issue.

  • 0
    Avatar
    Darrin Robinson

    We are also getting errors and it's 6:20PM EST.

  • 0
    Avatar
    Ricardo Fermino

    Hey folks... any news? I´m still receiving ERR_CONNECTION_RESET. Do you think the services will be normal at monday?

  • 0
    Avatar
    Chang Hong Chen

    Update please, I think six hours came and went.  No not Monday please.  I am resorting to using Dropbox to roll out my source code to my development team now...

  • 0
    Avatar
    Michal Ejdys

    looking forward to an update on the progress!

  • 0
    Avatar
    Chris Fischer

    This is giving the "cloud" a bad name...

  • 0
    Avatar
    Chang Hong Chen

    It seems http://www.cloudforge.com/ is down too, or just me

  • 0
    Avatar
    Nancy Stronczek
    Somebody's reading these comments because they updated the date after Sergio Castineyras pointed out the date discrepancy.
  • 0
    Avatar
    Roberto Leonel Gracias Ramos

    I have problems too

    svn: E175002: Commit failed (details follow):
    svn: E175002: Connection reset

  • 0
    Avatar
    Jonathan Daley

    I just received this from the CloudForge help desk:

    Mark Lovell (CloudForge Support) 

    Feb 21, 17:29 

    Hello, 

    The maintenance outage has been extended to 4:30 am UTC, and this has been updated on the notification page. Were sorry for the delay and are working as quickly as possible to complete all of the needed work. 

    Mark Lovell
    Collabnet Support

  • 0
    Avatar
    josh rothe

    This is actually pretty ridiculous. We have been unable to commit updates for the better part of the entire day. I have never had an outage like this with any of the other providers we have used before. What is going to be the resolution to make an entire day+ of downtown acceptable?

  • 0
    Avatar
    Dave Thompson

    I'm with Josh here, I think it's about time I moved providers. Sorry Cloudforge, but I can't just stop working all Saturday night with a deadline on Sunday because you guys can't patch a few servers.

  • 0
    Avatar
    Wade Wright

    I too will be leaving. This cost me a customer today. 

Article is closed for comments.