Slash Boxes

SoylentNews is people


Log In

Log In

Create Account  |  Retrieve Password

Site News

Join our Folding@Home team:
Main F@H site
Our team page

Funding Goal
For 6-month period:
2019-01-01 to 2019-06-30
(All amounts are estimated)
Base Goal:


Covers transactions:
2019-01-01 00:00:00 ..
2019-01-12 01:33:11 UTC
(SPIDs: [1022..1031])
Last Update:
2019-01-13 15:56:06 UTC

Support us: Subscribe Here
and buy SoylentNews Swag

We always have a place for talented people, visit the Get Involved section on the wiki to see how you can make SoylentNews better.

posted by martyb on Thursday January 10, @06:07PM   Printer-friendly
from the we're-baaaaaack! dept.

[Updated to correct time of neon CPU's spiking. --martyb]

We experienced an unexpected outage of the site this morning (20190110 00:15-07:45 UTC). At shortly after midnight approximately 0415 (UTC), CPU usage on neon suddenly pegged at 400% and things went downhill from there. Am not sure at this point what happened between 0015 and 0415.

Root cause is being investigated, but for now it seems the site is back up and working. Please let us know if you have any issues.

Note: you may need to have your browser ignore its cache (e.g. refresh with Ctrl+F5) and bring down everything fresh.

FWIW, system came back up after we rebooted neon (using the Linode manager page), and then bounced varnishd on fluorine and hydrogen (/home/bob/bin/bounce on each.)

Many thanks go to SemperOSS and cosurgi for problem determination and steps to rectify and FatPhil for his cheerleading!

[Update: TMB] So, the deal was that some unknown time in the past the ndb database node on helium had gone down. This wasn't a problem since we run a clustered database but nobody noticing it was. Then last night something caused neon to lose its cheese. Since it hosts the other node of the db, we had no db for a while. Bytram(martyb) has sysadmin powers for when unpleasant substances of various types hit the fan and thankfully he knew enough to get the neon db node back up and bounce apache/varnish on the web frontends, so kudos to him and all the folks who were backseat driving at the time due to lack of admin perms on their parts.

My brain's currently fried from going from asleep to OMGWTFBBQ without so much as a cup of coffee and a cigarette first, so I'm not going to dig into the root causes until it unfries itself but as a stopgap we have four more staff with shiny, new admin access that I'll be emergency bootcamping in the very near future. There's also going to be some monitoring reimplemented very soon so we notice this kind nonsense before it blows up in our faces again. I'll either update and bump this story or post a new one if we manage to figure out what the root causes were but at the moment the logs aren't being particularly helpful.

Original Submission

posted by The Mighty Buzzard on Wednesday January 09, @12:59PM   Printer-friendly
from the better-late-than-never dept.

While shutting down terminal windows to the SN servers this morning, one of them had the create table syntax for the comments table still on screen. I gave it a read through just because it was there and noticed that there wasn't an index for the opid (top level comment id for speeding up entire thread pulling) column. So I got some before numbers, added one, and ran some After tests. Heavily commented stories show a 50-150% pages-per-second speed increase in threaded views. Low hanging fruit FTW.

posted by The Mighty Buzzard on Tuesday January 08, @04:32PM   Printer-friendly
from the spit-and-baling-wire dept.

After a morning of slow query logging and cussing, a misplaced "GROUP BY" that was turning a 0.04 second query into one that took over fifteen seconds has been fixed. I'll leave the slow query log running overnight though just to make sure I didn't miss any less common ones. If you're still seeing any serious site slowdowns, let us know.

posted by martyb on Sunday December 30, @03:00PM   Printer-friendly
from the what-we-had-here-was-a-problem-to-communicate dept.

First off, it's been a week since we published Meta: The End of the Year is Nigh; End-of-the-Year Summary and Subscription Request and I am pleased to report we have received nearly $1000 in site subscriptions. Please accept my sincere and heartfelt thanks to all who have contributed! We are looking for another $1000 to make our funding goal. If you can help out either by starting a subscription, or extending a current one, that would be greatly appreciated! We have had a few people subscribe for $100; any amount you can provide will mean a lot.

As for IRC: it was brought to our attention a couple days ago that there was an issue in gaining access to SoylentNews' IRC securely.

tl;dr: Secure access to IRC should be functional; please reply in comments (with steps to reproduce) if you are still having issues. Read on for the scoop.

TheMightyBuzzard recently updated our Let's Encrypt certs across all of SoylentNews as they were set to expire on December 27. (Certs are issued with a 3-month duration.) Everything seemed to be working fine, so he took off on a much-deserved, week-long vacation.

I saw messages on IRC that there were issues in attempting to gain secure access to IRC. I thought that was strange as I was having no difficulty accessing it using HexChat on my PC. I tried the link on the SoylentNews home page: IRC and was also able to connect without issue. As the reports I'd seen were of the form "IRC is broken", and it was obviously working for me... now what? Pushed back asking for more details on steps to reproduce.

Some back-and-forth discussion (on IRC) isolated the problem to being involved with the recently-installed certs. They were in the correct location. They had the correct file permissions (read/write/execute). The irc daemon was running.

What could it be?

Kudos to audioguy who dove in and via guidance from Deucalion (our IRC master who was also on vacation and who was answering questions without benefit of being able to see what audioguy was looking at) was able to isolate the problem to incorrect Access Control List (ACL) settings for irc. AFAIK, nowhere else on the site do we use those — let's just say that IRC is a strange beast and leave it at that.

So, audioguy got the ACLs straightened out... yay! But it was unclear how to get ircd to actually use them. (There is a script for that but we didn't know it at the time) I had a chat (on IRC!) with chromas which worked out the command needed to restart the irc daemon (sudo kill -hup $irc_PID) and... voila! Back in service!


Oh! Anybody wondering how some of us were having no trouble securely using IRC through all this? Figured it out? Up until the move to Let's Encrypt, we used self-signed certs. I, as well as several others, still had those loaded on their system and they had not yet expired. Also, many of us were accessing irc using a 'bouncer' which would hold the connection to the daemon open and buffer transmissions between the server and our client. Connections to the bouncer were, thankfully, unaffected.

NOTE: We still have our alternate irc server, creatively named irc2, to bring forward but that can wait until staff is back from vacations.

P.S. Here's wishing all of you a Happy New Year!!!

P.P.S. When I wrote this, the fortune appearing at the bottom of the page read: "All is well that ends well. -- John Heywood".

Original Submission

posted by martyb on Sunday December 23, @08:00AM   Printer-friendly
from the blame-ncommander-for-showing-me-how-to-write-a-wall-of-text dept.

So it's not the end of the world as we know it, but it's nearly the end of the calendar year. How'd we get here, where are we at, and what have we been up to? Oh, and please send us some monies.


It all started with slashdot attempting to push a redesigned UI (User Interface) onto the community (aka the "Beta"). There was tremendous discontent with the decision which culminated in the The Slashcott. Some like-minded folk getting together and bashing an unmaintained open-sourced version of slashcode into working order. For some of the early pre-history of the site there is a very readable entry at This was a Herculean task, but they somehow managed in a couple week's time to get something running and opened it up to the world on February 16, 2014. The site had some "stability issues" at first, but these tenacious folk persevered and we are now fortunate to have a stable and functioning discussion system that is fast approaching five years of operation!

Some Statistics:

Since that inauspicious beginning we have seen:

  • 125 polls offered
  • 1,000 subscriptions to the site
  • 1,770 days of operation
  • 3,655 stories published to users' journals
  • 7,228 userids registered
  • 25,038 stories published to the site
  • 30,747 story submissions
  • 37,744 poll answers
  • 524,622 comment moderations
  • 772,179 comments posted

Check out the Hall of Fame for some additional statistics.


It bears mentioning that this site and its operations are supported entirely by volunteers. Nobody has ever received any payment for their efforts. In my own case, I work retail and have no two weeks' schedule the same. During the holiday season work hours are extended; as an example, I am scheduled to work past midnight tonight and the same again tomorrow. There have been many times I have popped into the site during a break and (painfully) used my mobile phone to push out a couple stories. Others here also have outside activities and commitments yet make the time to keep this site up and running.

Deucalion keeps us cats herded and keeps an eye on our IRC (Internet Relay Chat) daemons. The Mighty Buzzard handles the vast majority of actual site maintenance and security certs as well. Audioguy and Mechanicjay quietly work behind the scenes and take care of e-mail as well as other sysadmin-y tasks. Ncommander and paulej72 hover around in the background to help out when needed. Then we have fyngyrz, xyem, and FatPhil who pop in and help out from time to time. Lastly, there are the editors who are the main face of the site. Theirs is the seemingly thankless task of choosing story submissions, making corrections as needed, and queuing them up to appear on the main page. To all of you, I offer a profound and deep "THANK YOU!"

[TMB Note: He's being modest and left out that he's both Editor in Chief and HMFIC of breaking all of the things.]

I would be remiss in not mentioning the many others who were critical in the site's creation and launch who have since moved on to other projects -- though they no longer contribute to the site, their efforts were key at the time and we would not be where we are today without their efforts.

We have a tight-knit group behind the scenes, but generally go about things with a sense of humor. If you'd like to be a part of what makes this site what it is, and are willing to work with our sometimes curmudgeon-ly group, just send an e-mail to "admin [at]" or mention it in the comments.


Though the staff is entirely volunteer, there are still actual costs to keeping this site operational: monthly server bills, domain fees, accountant charges for filing taxes, and the like.

We have never carried advertisements on this site. Thanks to the continuing generosity of the community, we hope to keep it that way.

As of this writing, of our $3,000 funding goal for the second half of the year, we have received approximately $1142.48 -- that's just 38.1%.

If you have already contributed, THANK YOU! (If you are in a position to do so, please consider extending your subscription.)

We have approximately 110 users who had previously subscribed to the site, and have logged into it in the past 30 days, whose subscription has lapsed. I'll be the first to admit that our reminders are not the best! Maybe that happened to you?

If you wish to remain anonymous, designate your subscription as a gift; by default it goes to "mcasadevall" who has UID 6.

You can check your subscription status on the Subscribe page. Specify whatever amount you'd like (the amount presented is the minimum required for that duration) and submit it. We accept payments via PayPal and Stripe. (NOTE: For Stripe payments, Javascript must be enabled as we link to their payment processing page and it requires Javascript.)

Whatever amount you choose IS appreciated!! Please subscribe now.

It's not just the numbers!

The thing that keeps me volunteering here, though, is not the minutia of site operations (though I have learned so much by watching pros at work!). It is the community. I've come to know and appreciate the points of view of many regular commenters here. I'm regularly reminded people just don't fit into simple, compartmentalized boxes. Certain grand strokes may be consistent, but I've lost track of the number of times when a post has caused me to step back and go "Whoah!" Some deeply-held thought or belief gets re-examined and I'm a better person for that introspection.

The Subject Matter Experts (SMEs) also keep me coming back for more. These folk know stuff about areas that I didn't even know were areas! I am humbled by their contributions; more detailed than the press kit blurbs, but not so erudite that I need to grok the entirety of their specialty.

Whatever your interest or contribution, SoylentNews is People! Thank-you seems so little, but mine is heart-felt. Thank-you to all of you who contribute to this site, whatever way that may be.

Original Submission

posted by janrinok on Thursday October 18, @01:00PM   Printer-friendly
from the always-look-on-the-bright-side-of-life dept.

Some of you will recall that I recently underwent several bouts of surgery and, despite your welcome comments and good wishes, your best guesses that I was having a sex change, having my breasts enhanced in either size or number, or receiving some fairly radical treatment for hemorrhoids, were all fairly wide of the mark. The surgery is now long past and I have made a reasonable recovery for someone of my age. But I do wish to thank you all for your comments because, almost without exception, they raised a smile when things were not going too well for me.

My wife suffers from a severe medical condition and I have been her full-time carer for over a decade now. Although I wish she had never developed the condition, I expend great effort, and also receive considerable personal satisfaction, in providing many hours of care each day so that she can remain in our home and we can continue our lives to the fullest extent possible. However, she has recently suffered from a deterioration in her condition. This was not unexpected but no-one could say when the next problems would affect her. But the result is that I now have to provide more support to her and my free time is reduced.

I joined this site at its inception and have enjoyed every minute of my time here. But I cannot dedicate the time that role of Editor-in-Chief (E-in-C) deserves and, several weeks ago, I made the difficult decision to stand down from the post. (I can hear the cheering from some in our community even here in France!) The fact that most of you will not have noticed any of this means that the transition has been successful. The entire editorial team (which is nowhere near as large as that phrase makes it sound!) has stepped up to the plate and has maintained the output as it was before, ably led by Martyb who has assumed the role as E-in-C in addition to his numerous other roles on this site. I am grateful to them for their efforts and support both during my time as E-in-C and more recently in their work in editing the stories that we read each day. Thanks guys, you do a tremendous job with relatively little recognition. I've asked the powers-that-be to increase your salaries by an appropriate percentage.[*] I am also grateful to the other folk who do so much in the background keeping this site on-line. You have all become good friends although we could be standing next to each other and wouldn't know it.

Equally important to the site's success are you - the community. You provide the submissions, the comments, the funding, and you are the reason that we have a site at all. I thank each and every one of you for your contribution; from the regular submitters, the ACs, the 'characters', and those of you who just visit to read the stories that we publish. If I have offended anyone then I apologise but being E-in-C has been likened to herding cats in the dark: an almost impossible task and one in which you are certain to make a few mistakes.

Hopefully, I will remain on the site as an editor making whatever contribution I can. But, for the next few months at least, that contribution will be minimal as I have to solve several practical problems on how to make our home function satisfactorily for us both. I trust that you will give Martyb and the team the same support in the future that I have been fortunate enough to enjoy over the past couple of years. Thank you.


[*] Clarification: This is an inside joke among the staff. Nobody here receives any kind of payment for their efforts on the site; we are strictly volunteers. So, a 20% raise on zero is... still zero. --martyb

posted by martyb on Wednesday October 10, @03:00PM   Printer-friendly

As you probably have noticed, our site has been a bit sluggish lately.

We are aware of the issue and are developing plans for dealing with it. The primary issue lies in the database structure and contents. On-the-fly joins across multiple tables cause a performance hit which is exacerbated by the number of stories we have posted over the years (yes, it HAS been that long... YAY!). Further, stories which have been "archived" — allowing no further comments or moderation — are still sitting in the in-RAM DB and could be offloaded to disk for long-term access. Once offloaded, there would be much less data in the in-RAM database (queries against empty DBs tend to be pretty quick!) so this should result in improved responsiveness.

A complicating factor is that changing the structure on a live, replicated database would cause most every page load to 500 out. So the database has to be offlined and the code updated. That would likely entail on the order of the better part of a day. Obviously, shorter is better. On the other hand "The longest distance between two points is a short cut." We're aiming to do it right, the first time, and be done with it, rather than doing it quick-and-dirty, which usually ends up being not quick and quite dirty.

So, we ARE aware of the performance issues, are working towards a solution, and don't want to cause any more disruption than absolutely necessary.

We will give notice well in advance of taking any actions.

Original Submission

posted by The Mighty Buzzard on Friday September 14, @01:30PM   Printer-friendly
from the necessary-roughness dept.

Pardon the short but unscheduled/unannounced site interruption. The cluster backend for our database needed to be resized as it was over 90% full and was causing performance issues. Hopefully it should all be taken care of now and shouldn't need poked at for another couple years at least.

posted by The Mighty Buzzard on Wednesday August 29, @01:32PM   Printer-friendly
from the head-meet-desk dept.

Gift subscriptions from ACs (Anonymous Cowards) are working again. If you're curious what was broken, have a look.

If you attempted to make a gift subscription as an AC since early to mid May, and received an error, please try again at: (Or click the link in the "Navigation" Slashbox).

As is standing SN policy, martyb is to blame for anything warranting blame. =) You can go about your business. Move along.

posted by martyb on Monday August 20, @11:45AM   Printer-friendly
from the teamwork++ dept.

We strive for openness about site operations here at SoylentNews. This story continues in that tradition.

tl;dr: We believe all services are now functioning properly and all issues have been attended to.

Problem Symptoms: I learned at 1212 UTC on Sunday 2018-08-19, that some pages on the site were returning 50x error codes. Sometimes, choosing 'back' in the browser and trying to resubmit the page would work. Oftentimes, it did not. We also started receiving reports of problems with our RSS and Atom feeds.

Read on past the break if you are interested in the steps taken to isolate and correct the problems.

Problem Isolation: As many of you may be aware, TheMightyBuzzard is away on vacation. I logged onto our IRC (Internet Relay Chat) Sunday morning (at 1212 UTC) when I saw chromas had posted (at 0224 UTC) there had been reports of problems with the RSS and Atom feeds we publish. I also noticed that one of our bots, Bender, was double-posting notifications of stories appearing on the site.

While I was investigating Bender's loquaciousness, chromas popped in to IRC (at 1252 UTC) and informed me that he was getting 502 and 503 error codes when he tried to load index.rss using a variety of browsers. I tried and found no issues when using Pale Moon. We tried a variety of wget requests from different servers. To our surprise we received incomplete replies which then caused multiple retries even when trying to access it from one of our SoylentNews servers. So, we surmised, it was probably not a communications issue.

At 1340 UTC, SemperOss (Our newest sysadmin staff member... Hi!) joined IRC and reported that he, too, was getting retry errors. Unfortunately, his account setup has not been completed leaving him with access to only one server (boron). Fortunately for us, he has a solid background in sysops. We combined his knowledge and experience with my access privileges and commenced to isolate the problem.

(Aside: If you have ever tried to isolate and debug a problem remotely, you know how frustrating it can be. SemperOss had to relay commands to me through IRC. I would pose questions until I was certain of the correct command syntax and intention. Next, I would issue the command and report back the results; again in IRC. On several occasions, chromas piped up with critical observations and suggestions — plus some much-needed humorous commentary! It could have been an exercise in frustration with worn patience and frazzled nerves. In reality, there was only professionalism as we pursued various possibilities and examined outcomes.)

From the fact we were receiving 50x errors, SemperOss surmised we were probably having a problem with nginx. We looked at the logs on sodium (which runs Ubuntu), one of our two load balancers, but nothing seemed out of the ordinary. Well, let's try the other load balancer, on magnesium (running Gentoo). Different directory structure, it seems, but we tracked down the log files and discovered that access.log had grown to over 8GB... and thus depleted all free space on /dev/root, the main file system of the machine.

That's not a good thing, but at least we finally knew what the problem was!

Problem Resolution: So, we renamed the original access.log file and created a new one for nginx to write to. Next up came a search for a box with sufficient space that we could copy the file to. SemperOss reported more than enough space free on boron. We had a few hiccups with ACLs and rsync, so moved the file to /tmp and tried rsync again, which resulted in the same ACL error messages. Grrrr. SemperOss suggested I try to pull the file over to /tmp on boron using scp. THAT worked! A few minutes later and the copy was completed. Yay!

But, we still had the original, over-sized log file to deal with. No problemo. I ssh'd back over to magnesium and did an rm of the copy of the access.log and... we were still at 100% usage. Doh! Needed to bounce nginx so it would release its hold on the file's inode so it could actually be cleaned up. Easy peasy; /etc/init.d/nginx restart and... voila! We were now back down to 67% in use.

Finally! Success! We're done, right?
Umm, no.

Did you see what we missed? The backup copy of access.log was now sitting on boron on /tmp which means the next system restart would wipe it. So, a simple mv from /tmp to my ~/tmp and now the file was in a safe place.

By 1630 UTC, we had performed some checks with loads of various RSS and atom feeds and all seemed well. Were unable to reproduce 50x errors, either.

And we're still not done.

Why/how did the log file get so large in the first place? There was no log rotation in place for it on magnesium. That log file had entries going back to 2017-06-20. At the moment, we have more than sufficient space to allow us to wait until TMB returns from vacation. (We checked free disk space on all of our servers.) The plan is we will look over all log files and ensure rotation is in place so as to avoid a recurrence of this issue.

Problem Summary: We had a problem with an oversized logfile taking up all free space on one of our servers but believe we have fixed it and that all services are now functioning properly and all issues have been attended to.

Conclusion: Please join me in thanking chromas and SemperOss for all the time they gave up on a Sunday to isolate the problem and come up with a solution. Special mention to Fnord666 who we later learned silently lurked, but was willing to jump in had he sensed we needed any help. Thank-you for having our backs! Further, please join me in publicly welcoming SemperOss to the team and wishing him well on his efforts here!

Lastly, this is an all-volunteer, non-commercial site — nobody is paid anything for their efforts in support of the site. We are, therefore, entirely dependent on the community for financial support. Please take a moment and consider subscribing to SoylentNews, either with a new subscription, by extending an existing subscription, or making a gift subscription to someone else on the site. Any amount entered in the payment amount field, above and beyond the minimum amount is especially appreciated!

Original Submission

posted by martyb on Wednesday July 18 2018, @11:00AM   Printer-friendly
from the steady-as-she-goes dept.

First the good news. I just received word that janrinok, our Editor-in-Chief, is finally out of the hospital and back in his own home! He is very tired and has severe restrictions on his activities but is otherwise in excellent spirits. He very much appreciated the kind thoughts and wishes expressed by the community in our prior stories. It will still be many weeks or months before he can resume his prior level of activities on SoylentNews, but hopes to pop in once in a while to "second" stories that are in the story queue. Please join me in welcoming him back home!

Next, the good news. In janrinok's absence, the other editors have stepped up to the challenge. I'd like to call out chromas, fnord666, mrpg, and takyon who have all freely given from their spare time to make sure we have a steady stream of stories appearing here. I even saw CoolHand pop in on occasion to second some stories! teamwork++

Then, I have to bring up the good news that our development and systems staff have kept this whole thing running so smoothly. Besides the site, there is e-mail, the wiki, our IRC server, and a goodly number of other processes and procedures that make this all happen. That they are largely invisible attests to how well they have things set up and running!

Lastly, the good news. This is what's known in the press as the "silly season". Summer in the Northern Hemisphere means most educational institutions are on break, so less research is done and reported. other ventures are closed or running on reduced staffing levels. In short, the amount of news to draw from is greatly diminished. Yet, even in that environment, the vast majority of the time finds us with a selection of stories in the submissions queue to draw from.

We recently hit a low spot where I combed the web for a couple quick stories I could submit, but that has been the exception rather than the rule. Generally, we look for stories that have some kind of tech-related angle to them. The community has spoken loud and clear that there are plenty of other sites to read about celebrities, politics, and religion. We make a slight nod to politics in so much as it affects technical areas or has large scale ramifications (e.g. a story about President Trump having a meeting with Russian president Vladimir Putin would fit that description). Even then we generally try to keep it down to one story per day.

That said, if you see a story on the 'net that catches your fancy, please send it in! Feel free to draw upon titles listed on our Storybot page, then pop onto IRC (Internet Relay Chat) and simply issue the command ~arthur $code where $code is taken from the second column on the Storybot page.


Whether you contribute by submitting a story, buying a subscription, writing in one's journal, moderating or making a comment, we continue to provide a place where people can discuss, share knowledge and perspectives, and maybe learn a thing or two, too!


Original Submission

posted by martyb on Tuesday July 10 2018, @10:33PM   Printer-friendly
from the watching-out-for-one-of-our-own dept.

As you might recall, in an earlier story we noted that SoylentNews' Editor-in-Chief, janrinok, was scheduled for a medical procedure.

I have just received word that there were some (not totally unanticipated, but thought to be a very unlikely) complications and the expected 3 day hospital stay has now lasted over a week. In his own words:

No idea what will happen next is anybody's guess. My first objective is to be well enough to get home again but that looks like being the end of the week at the earliest.

He seemed to be in good spirits. In his inimitable style of humor, he noted the internet connection available to him in Hospital would lie in the bottom-most tier of our current poll!

I am torn in revealing personal details that were shared with me, and wish to not sound overly alarmist. I'll just leave here that I am reminded of a saying by Ralph Waldo Emerson "You cannot do a kindness too soon, for you never know how soon it will be too late."

JR has tirelessly (and tiredly, too) gone over and above in support of this site -- please keep him in your thoughts and, if you are of a mind to, your prayers. --martyb

Original Submission

posted by martyb on Monday July 02 2018, @02:30PM   Printer-friendly
from the teamwork++ dept.

This is a followup to: SoylentNews Site Certificates Expiring... We ARE Working on It, But... [Updated]
and: Site Services Restored

Certs (Not Just a Breath Mint):

Thanks to the efforts of The Mighty Buzzard and NCommander we now have valid certs, issued by LetsEncrypt installed on all of our servers. Except that the IRC server needs to be bounced to make its cert active on the backup daemon, all should now be in effect. As in our original story, you can check our certificate status with these links:


The past few days have brought into focus a situation that has been building for several months: We really only have a single person who is working on developing features for the site, The Mighty Buzzard. As with any large and on-going undertaking, this burden is taking its toll. I try to help out as I can, but as I am the primary QA/Test guy who is much better at the user-facing things than what all happens "under the covers", my abilities and assistance are limited. If you have any spare time and would like to lend a hand (and every bit helps), please reply in the comments or contact The Might Buzzard directly on IRC.


I recall in the early days of this site when things would fall over several times a day. That has largely become a thing of the past... to the point where it is unusual for any issues to appear on the site and the support services we maintain (email, wiki, IRC, etc.) The baseline code on which this site was founded (open-sourced, out-of-date, back-level, and non-functional) was not promising, but the staff managed to bludgeon it into shape and we now have a solid foundation. That it continues to run as smoothly as it has is a testament to our SysOps folk who toil largely in the background and just keep things working... as well as the continued care-and-feeding that TMB so generously provides. To all of you, please accept my heartfelt thanks and appreciation!

Some numbers: we are approaching the 23,000th story posted; have recently passed 700,000 comments submitted; have had over 3,300 journal articles posted; and are on the cusp of having our 120th Poll!

Though all numbers are approximate and unofficial, it appears we surpassed our funding goal for the first half of the year ($3,000) with a net subscription tally of just over $3,250! I'll leave it to our treasurer to collate and post the official numbers. I'll leave the "Funding Goal" side bar as is for a week or so to commemorate this accomplishment. Do note that subscriptions are still being accepted and will count towards the second half of the year's funding needs.

Folding@Home: Not all of you may be aware, but our soylentnews team for Folding@Home is currently at 240th place... in the world! It started with a single story posted to this site. Just over four years ago, we were at 230,319th place! If you have any spare computes you would like to contribute, especially GPU-based, we'd love to have you sign up! Just reply in the comments and I'm sure someone will get back to you.

Whenever I write one of these stories, I always fear I'll have omitted someone or something important. Please accept my humble apologies if I have done so as there is no intent to slight any contributor.

To the community, I offer my thanks for your contributions to the site as well as your patience and understanding during the challenges of the past few days. Contributions are not just financial (though we wouldn't be here without them -- Thank You!), but also submitting stories and comments, and moderating comments, too! The community continues to impress me with your wide-ranging knowledge and expertise; I have learned much from the exchanges in the story comments!

Lastly, please keep janrinok (our Editor-in-Chief) in your thoughts and wishes while he undergoes a medical procedure and attendant recovery period. Best of luck JR!


Original Submission

posted by NCommander on Sunday July 01 2018, @01:33AM   Printer-friendly

Just a quick note, as previously noted, our SSL certificates were due to expire. Due to various headaches involving issues changing our DNS records, and my personal unavailability, we were unable to renew our certificates in time. Right now, is running on a LetsEncrypt certificate that was issued after quite a bit of pain. We're still trying to fix the fundamental issues that prevented us from being issued a two year Gandi certificate. Currently, I'm unable to resolve this issue more in-depth, but I've granted access to TheMightyBuzzard to be able help handle the necessary issues that caused the downtime. I will try to get a full writeup of the situation, but for the time being, the main site is up. Secondary services remain down due to the same renewal issues.

Apologies for any inconvenience,


posted by martyb on Saturday June 30 2018, @03:20PM   Printer-friendly
from the certs-are-not-just-a-breath-mint dept.

[Updated 2018/06/30 15:19:00 UTC. I've received word that "certificate renewed, but hasn't been issued" and that it will be installed as soon as we receive the new cert. Original story follows. --martyb]

We've been up front with the community right from the start... and intend to keep doing so in the future.

Where we are at:

We have encountered an issue with Lets Encrypt (LE), the certificate issuer for the majority of our [sub]domains. Even though we can 'see' these domains from any number of different servers... for some unknown reason, LE fails to see them. So, at the moment, we are unable to get them to generate certs for us.

Separately, the cert for is handled by Gandhi. As far as I understand it (and I'm no sysadmin so take this with a healthy dose of salt) there are only two members of our staff who have the ability to update that cert. (We obviously don't want to let world+dog have access to that, right? My guess is that at that time, having a couple people seemed sufficiently redundant and secure).

What it means to you:

You may encounter a warning from your browser when trying to access the site that a certificate has expired. I cannot speak for all browsers, but I've generally seen that along with the warning is an option to trust the cert anyway. (Note: along with allowing that exception, I've sen at least one browser default a checkbox to make the exception permanent. It's entirely up to you, but I see no reason to make it a permanent exception at this point.)

We are working on it, and obviously hope to have things straightened out sooner than later! On the other hand, should things go sideways, I want to keep the community informed about what's up, what's happening, and what you can expect.

Checking status:

If you would like another means to check on the status of the certs, Comodo makes it easy with queries such as these:


If the site becomes unavailable because of an expired cert, yeah, we know and we're working on it. Accept a temporary exception in your browser and we'll let you now when things are back to normal.


P.S. Our Editor-in-Chief, janrinok, is currently undergoing preparations for a medical procedure... it's hard to say at this point, but it's likely he may be unavailable to help with the site for a couple weeks. Please join me in wishing him well for the procedure and for a speedy recovery!

Original Submission