SoylentNews is people
SoylentNews
As many of you noticed, we had a site crash today. From around 1300 until 2200 UTC (2021-05-20).
A HUGE thank you goes to mechanicjay who spent the whole time trying to get our ndb (cluster) working again. It's an uncommon configuration, which made recovery especially challenging... there's just not a lot of documentation about it on the web.
I reached out and got hold of The Mighty Buzzard on the phone. Then put him in touch with mechanicjay who got us back up and running using backups.
Unfortunately, we had to go way back until April 14 to get a working backup. (I don't know all the details, but it appears something went sideways on neon).
We're all wiped out right now. When we have rested and had a chance to discuss things, we'll post an update.
In the meantime, please join me in thanking mechanicjay and TMB for all they did to get us up and running again!
(Score: 0, Disagree) by Anonymous Coward on Friday May 21 2021, @11:28AM (7 children)
Money talks.
(Score: 0) by Anonymous Coward on Friday May 21 2021, @02:17PM
What utter nonsense. This site is run by volunteers and the staff (including TMB) have been excellent.
(Score: 2) by janrinok on Friday May 21 2021, @02:21PM (4 children)
MartyB is responsible for recording donations, and he has been rather busy for the last year or two - not TMB. Anything you else you want to accuse TMB of while you are at it?
(Score: 1, Interesting) by Anonymous Coward on Friday May 21 2021, @03:19PM (3 children)
Plenty of people saw buzz as a large part of the problem. After a week of “playing nice” he packed it in.
If you had even ONE serious developer on tap you could have a different CMS up and running in a day, stories, comments, user journals, stupid polls, etc. ONE DAY. Take a few weeks to get user feedback, tweak things a bit, etc.
But NOBODY with a clue wants to maintain a mess of obsolete Perl that has no documentation. It’s one of those cases where you have to close your eyes and ignore the sink costs of the time and emotions tied up in rehash.
Software development is brutal. You can’t be sentimental over old code. You need to “knife the baby” on a regular basis to progress. Otherwise we’d still be stuck with GWBASIC.
(Score: 3, Informative) by janrinok on Friday May 21 2021, @04:49PM
The Perl code is working as expected. This is a system configuration problem. Stop trying to fix the wrong problem.
(Score: 5, Informative) by DECbot on Saturday May 22 2021, @03:06AM
To add to what Janrinok has said, slashcode regularly handled a traffic load that would take offline mainstream static sites and ddos ISPs with less resources then what people throw at a regular Wordpress or Drupal sites today. The perl code is proven, mysql is proven, but there is a configuration issue causing stability issues with the SN implementation of the slashcode. That is what needs to be addressed. It's not time to replace the horse cause it threw an ill fitting shoe.
cats~$ sudo chown -R us /home/base
(Score: 2) by bzipitidoo on Sunday May 23 2021, @03:08AM
One day, for one person to do a migration to another CMS? You're dreaming. I am not familiar with CMSes, but if it's anything like a database migration, you're talking weeks at the least. Yeah, one expert could migrate a little toy of a database in one day, but a real one with millions of rows and complexities such as stored procedures and non-standard SQL, no way.
(Score: 2) by Tork on Friday May 21 2021, @04:03PM
He 'shit' on everything by babbling just like I do. If I couldn't take his silliness I certainly wouldn't be able to deal with the AC-holes around here. (I'll leave it ambiguous for now whether or not I'm including you in that.)
I'm not 'in love with my abuser', my panties are simply wrinkle-resistant.
🏳️🌈 Proud Ally 🏳️🌈