Evilshy 5,090 March 7, 2012 Share March 7, 2012 Just wondering why? Or was it scheduled and I missed the memo? Signature now 99% less edgy! Link to comment Share on other sites More sharing options...
Electrobolt 2,069 March 7, 2012 Share March 7, 2012 May have been a crash or something... But I won't swear to it. We'll just have to wait for Feld0's response Electrobolt | Grand Journeys Link to comment Share on other sites More sharing options...
Vicke 3,189 March 7, 2012 Share March 7, 2012 Crashes happen... And it was back up after like 5-10min? Signature made by Kyoshi Link to comment Share on other sites More sharing options...
Evilshy 5,090 March 7, 2012 Author Share March 7, 2012 Yes, I know that crashes happen, I just wanted to know if there was some other reason for it. Signature now 99% less edgy! Link to comment Share on other sites More sharing options...
Orien 3 March 7, 2012 Share March 7, 2012 Sorry, our Twitter has some details... https://twitter.com/#!/cleverkite Link to comment Share on other sites More sharing options...
Founder Twilight Sparkle ✨ 8,526 March 7, 2012 Founder Share March 7, 2012 There was a server problem earlier this morning that had nothing to do with MLP Forums or any of my other sites (other than the fact that it took them offline). Here's a snippet from an email CleverKite sent me about it: Peter, Earlier this morning at 10:20am PDT, your node (bcloud) rebooted itself as part of an unexpected feedback loop. Under normal circumstances, this would have only caused downtime of a minute or two as the node comes back online. Unfortunately instead, the node's filesystem rebooted into read-only mode and decided that there were data inconsistencies after the reboot that needed to be processed through a lengthy fsck (filesystem check), during which all customer clouds would be inaccessible. At this point, we needed to ensure the integrity of all customer data on this node before fully restarting it, which takes time. 26 minutes later at 10:46am PDT, bcloud was brought back online without data loss along with all customer clouds on this node. We are still investigating the feedback loop that caused the reboot in the first place and will make changes to prevent it from happening again. We are deeply sorry for any inconvenience caused by this outage. These sort of thngs shouldn't be happening here and we're not happy about it. Sorry, our Twitter has some details... https://twitter.com/#!/cleverkite Orien, we all know that unexpected problems can happen, and I thank you for coming here and updating my own community on the downtime, as well as communicating about it so transparently. Avatar credit: robinrain8 Signature credit: Kyoshi Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Join the herd!Sign in
Already have an account? Sign in here.
Sign In Now