Outage: Master LDAP (resolved)

Your "99.9% uptime" is ticking. You will soon consume the entire year's commit.

or your .1% downtime is ticking, glass half full?

In one hour I switch to github.

My mistake, .1% was fully consumed the first week of the year: https://help.cloudforge.com/entries/23489316-Outage-production-database-db01-is-now-resolved

i should have said your .1% downtime is tocking ... if uptime ticks, downtime tocks?

anyway, tick tock ...

Urgent needed to sync with SVN . What is the expected time to fix this issue.

Have a build I need to sort in the next hour to ship out heh. Would also be interested in how progress goes :)

when they don't update progress stats that's a pretty good indication of how progress goes ... it doesn't ...

Oh give 'em a break. They're working on it and when they're done, they'll let us know.

Haven't you ever been there? I know I have.

Yes, we've been there; at an organization that doesn't have the availability they advertise, and those companies deservedly lose business. We aren't hacking on individuals, rather the organization that made claims that aren't met. We aren't saying people aren't doing the best with the resources they have currently, we are saying that after the organization already surpassed their downtime commitment in the first week of the year, they should have reset expectations or found other means to improve uptime.

Also, there's no excuse for not providing status updates when their core service is out. That's something that any person in the whole organization can do. Get the freaking owner on the web to come post here every half hour until it's fixed. Do it now.

0.1% is about 45min, so everybody should be requesting 7 free days because of this. I doubt they will drop below 97% though, it's about a day-long outage. But at that point I will not be looking for 2 free weeks of service, I will be switching.

Was up for 5 mins for me, then down again.

Sorry all, obviously this has been a huge pain for everyone. We didn't expect the LDAP slave to fail when our main LDAP server was unreachable. Shannon is correct; there is no excuse. Unfortunately, a lot of the time was waiting for engineers to resolve this, and by the time I sent out an ETA update to the support staff the problem was solved roughly 15 minutes later. We apologize that it took so long to resolve something that could have been easily avoided.

The update says all services are available- Git is still down for me. Is this working for other people yet?

Edward,

Strange.. can you try again real quick? I'm hoping there just needed to be a services resync

Still down for me, and my company.

same here..SVN is not still working for me . 

Looks like I spoke too soon.. once was up, now is down. Sorry all.. I've alerted the engineers.

Git is down for me, either!

Just tried again, pull/push hangs. My build server isn't able top connect either (see attachment) and even the cloudforge web interface (viewvc) hangs.

SVN is still not responding for me

SVN is still broken for me too

We've updated the status once again..I'm sorry to have misled. Apparently it was only up and healthy for a good 5-10 minutes. Our engineers are investigating as we type this.

Jesse Yowell

Support Engineer

Svn works for me from the command line. However, if I want to browse the repository, it won't connect.

Unfiortunately, this is not the first time.  I have been a customer since the "Dude" days and now I am looking elsewhere.

OMG, I just sign up and they have LDAP crash....  FAIL OF DAY

Just saw some signs of life again....  time will tell if steady or not.

Engineering said Main LDAP was brought back up. We're hoping it stays steady.. sorry for the eventful morning, everyone

Jesse it's still not working - svn is out for the count