MacSlash Public Service Announcement
From 5 minutes ago, via acaben of MacSlash.org...
The 3 year old Xserve which powers MacSlash died a painful death this afternoon. We've got full backups, and the drives in the Xserve are most probably fine, so we should be back up and running very soon. Just wanted to give you a heads up...
Just throwing it out there so that what readers we may share have an idea of what's going on, because I'm sure they'd do it for others. That's gotta be a shitty day, and from what I caught it sounds like their web hosting provder (digital.forest) is looking at getting their drives into a loaner XServe ASAP, so they'll be back online in one form or another. Before you ask, I'm told this includes the Canadian.
Posted by drunkenbatmanDecember 05, 2005, at 07:59 PM
Comments (17)
Posted by: Ben Stanfield at December 5, 2005 08:20 PM
We'll do a full run down on what happened once the triage is out of the way. At the moment, we're verifying the database, and hope to be back up soon.
Posted by: dhaveconfig at December 5, 2005 09:48 PM
y'know I'm sitting here myself repairing a 3-year old Xserve... and know two other people who've had them go down in the last month.
lucky it's only my dev box...
Posted by: Not a Fan of MacSlash at December 5, 2005 10:01 PM
What goes around comes around.
That's what you get for fascist moderation. Maybe next time around you'll let the readers moderate?
Posted by: also not a fan at December 5, 2005 10:53 PM
aaronvegh's posts alone put the site squarely in "fanboy rag" territory
Posted by: Evan Schoenberg at December 5, 2005 11:17 PM
Hey, 0.87b :)
Posted by: James Bailey at December 6, 2005 01:07 AM
>That's what you get for fascist moderation.
I don't get it, how does a hardware failure have anything to with macslash.org's moderation system? Are you saying if they allowed users to moderate ala slashdot then their hardware wouldn't have failed?
I think it was the elves, they're in it with the gnomes.
Posted by: Karma Coma at December 6, 2005 01:25 AM
Scientific studies have shown that good worldly karma results in 5 nines up-times.
Hmm, appropriate then that the comment "What goes around comes around" can be called "Karma" - which is also the metaphor used in slashcode sites' moderation systems.
What goes around really does come around.
Posted by: Malte at December 6, 2005 07:45 AM
Seems like it's up and running again..
http://macslash.org/
Posted by: Susan at December 6, 2005 08:48 AM
Remember the time trollaxor decided that G4 ibooks didn't have altivec, because he couldn't find mention of it in Apple's advertising?
Posted by: drunkenbatman at December 6, 2005 01:21 PM
What goes around comes around.That's what you get for fascist moderation. Maybe next time around you'll let the readers moderate?
I wonder how karma feels about schadenfreude...
Posted by: Tyler at December 6, 2005 04:25 PM
I wonder how karma feels about schadenfreude...
Karma most likely views schadenfreude as the ultimate enabler.
Posted by: Kurt Moore at December 6, 2005 05:35 PM
What Adium theme is that?
Posted by: Chris Williams at December 6, 2005 10:45 PM
It's PurePlastics with Gery vs Graphite variant.
What's up with not being able to use my yahoo email address to post?
Posted by: Erik Cronin at December 6, 2005 11:11 PM
Glad that macslash is back online... was starting to get the shakes.
Posted by: vastheman at December 6, 2005 11:44 PM
How come I keep getting mod points now that MacSlash is back online? I hadn't got mod points for about a year before the crash.
Posted by: Ben Stanfield at December 7, 2005 12:23 PM
Vastheman,
One of the side benefits of the server crash was that we took a few extra hours of downtime to run some database optimizations and fix broken tables. It appears that one of the tables related to moderation was corrupt, which is why some user accounts are now recieving tons of mod points. The system should stabilize at some point in the near future and go back to handing out mod points to those eligible on a regular, but less frequent, basis.
Oh crap ~ my Xserve is 3 years old! Hope we get more info on what went bad. Usually a hard drive is to blame, but that does not sound like the case here.