Stories
Slash Boxes
Comments

SoylentNews is people

Meta

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:
2022-07-01 to 2022-12-31
(All amounts are estimated)
Base Goal:
$3500.00

Currently:
$438.92

12.5%

Covers transactions:
2022-07-02 10:17:28 ..
2022-10-05 12:33:58 UTC
(SPIDs: [1838..1866])
Last Update:
2022-10-05 14:04:11 UTC --fnord666

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 Monday June 24 2019, @12:37PM   Printer-friendly
We are aware of issues when trying to access the site. First noticed at approx. 0300 UTC. Our servers look okay. It appears there may be issues with upstream connectivity.

Also, Linode is planning some server reboots over the next week or so. We will try to give advance notice and keep downtime to a minimum.

Update: Everything seems to have quieted down. Many many thanks to NotSanguine for jumping in and lending his expertise to help identify and isolate where things were borked.

Indications are that a bad BGP (Border Gateway Protocol) route was published causing a relatively small AS (Autonomous System) to have all traffic to/from a large fraction of the internet attempt to go through its routers.

posted by martyb on Tuesday June 11 2019, @04:00PM   Printer-friendly
from the passing-the-word dept.

As many of you are aware, SoylentNews uses Let's Encrypt certificates to protect the vast majority (all?) of our networking connections.

Under the watchful eyes of The Mighty Buzzard and SemperOSS I have updated our certs and deployed them across our servers and services. At this point, all seems to be working fine. That said, I have a well-earned reputation of being able to break nearly anything, so it would not entirely surprise me if you find something awry. If so, please let us know! You can comment on this story and/or jump over to the "#dev" channel on IRC and let us know there.

For completeness' sake, the updated certs were rolled out at 20190611_140630 UTC.

NOTE: Do be aware it takes time for updated DNS records to work their way across the internet, so if you do encounter a problem, try clearing your cache and trying again before assuming things are borked.


Original Submission

posted by janrinok on Monday May 27 2019, @03:45AM   Printer-friendly
from the easy-now dept.

Holiday Weekend: For our international readers who may be unaware, Monday 27 May marks Memorial Day in the United States, a remembrance of members of the military who have passed in the line of service. In reality, if has become the de facto start of summer which runs past Independence Day (July 4) until Labor Day.

Over this 3-day-long holiday weekend, a great number of establishments are closed or run at reduced hours and staffing. Stories appear on the internet at a reduced rate, and many more "fluff pieces" appear as filler.

I have heard quite clearly that, given a choice, the community generally prefers quality over quantity.

SoylentNews runs with approximate story spacings of a bit over 1.5 hours on weekdays and a little under 2.5 hours on weekends. We've been "feeding the queue" 24 hours per day, every single day, for over 5 years (still amazes me it has been that long!)

So, based primarily on those factors, I have suggested the eds adopt weekend story spacing for Monday (UTC) so they, too, can have a bit of a break.

Read on past the break for the rest of the site news.

Staffing: I would like to take this opportunity to formally welcome back fnord666 who had been on leave from the end of last year into early this year. Good to have you back! On the other hand, mrpg has recently moved and will be incommunicado until he is able to get situated again. Please join me in wishing him well! Our Editor-in-Chief emeritus is back in the saddle, too, though his circumstances may change at any time. He has many outside obligations and yet willingly gives of his very limited free time to SoylentNews. We are indeed fortunate to have him with us; thanks JR!

Outage: Well, it was not actually an outage, but on May 22, 2019 at approximately 2300 UTC, people started reporting issues with the site. Symptoms included some of the slashboxes on the side of the main page were not loading as well as some reports that CSS (Cascading Style Sheets) were failing to load causing malformed layout. I got wind of the issue just before midnight. It took me a couple tries to invoke the correct script to "bounce" the front-end servers (which basically just restarts apache on both our front-end servers and restarts the single slashd daemon). I promptly reported the outage and corrective measures to the community and it seems that all is functioning properly again. Please speak up in the comments if you are still experiencing any issues. But... be sure to clear your browser cache and do a hard reload of the site (e.g. Ctrl+F5 works on Firefox and derivatives) to make sure you are getting a fresh copy of all the files.

Finances: We have reached our funding goal of $2000 for the first half of 2019! Better still, we still have the rest of May and all of June remaining. I took the liberty of updating the "beg-o-meter" in the site news slashbox with a stretch goal of $1000. I am happy to report that we have already received $168.93 towards the stretch goal. I am so grateful for the support of the community for our efforts. For those who may be new or unawares, this is a purely volunteer organization. Nobody on staff has ever received any remuneration ($5 word for pay) for their efforts on this site. As I understand it, both NCommander and Matt_ incurred large monetary expenses in getting the site going and established legally as a Private Benefit Corporation based out of Maryland — expenses for which they have never been repaid. They have been more than patient and gracious in their insistence that SoylentNews become well enough established before getting repaid.

When you subscribe, some of the site limits are relaxed and you get a shiny star next to any comments you post. For the humble, you can turn that star's display off in your preferences.

If you wish to help out, click on Subscribe and select whether you want the subscription to start/extend your own subscription or you wish to make a gift subscription. If it is a gift subscription, specify the UID for the recipient. The default of UID==6 is that of Michael Casadevall (another nick NCommander used when setting up the site) or you may replace the UID with 2339 in memory of Michael David Crawford, or any other UID that you want.

Penultimately, select a subscription duration and amount (the suggested amount is a minimum; any in excess of that is greatly appreciated), and click on the Continue button. NOTE: Javascript needs to have been enabled for the following step to work. Lastly, choose your payment method of either Paypal or Stripe, fill in the requested details, and submit.

As I have mentioned before, this site has real expenses with server hosting fees, domain name registration, paying for a CPA to file our taxes, and the like. Those who support us financially help "keep the lights on." Thank You!

Submissions: This is not to take away from those who contribute to the site in other ways. Please accept my thanks to all of you who submit stories for the editors to poke at and bring to the community. Some of the community post stories to their journal which has led to many an interesting conversation. Above all, thank you to those who weigh in by posting comments. It is the primary reason for this site's existence, so please keep those comments coming!

Moderations: All comments are visible, but some have more visibility than others, thanks to moderation. For those who wish to see just the crème de la crème, set your comment threshold higher and give thanks to those who have performed moderations.

With respect to moderations, a user may moderate anywhere from 0 to 4 comments by another user. Any moderations in excess of 4 upmods or 4 downmods in a 24-hour period starting at 00:10 UTC will be reversed. It is our intention at some point to have the site impose that limitation automatically so no penalty is currently being imposed at this time. That means we need to monitor moderations and manually reverse those in excess of the limits. The short form of the moderation guidelines is "Don't be a jerk." On the other hand, 10 mod points are issued to every registered user at 00:10 UTC each day... please use them! Please try to focus on upmodding good (e.g. Funny, Interesting, Insightful, Informative) comments but don't be afraid to downmod (e.g. Offtopic, Troll, Flamebait) where appropriate.

When I moderate a comment, my thoughts are for the next person to come along; how can I help curate the discussion to best help them out?

Thank You! Thanks to all the rest of the staff who humbly trudge along behind the scenes to make it happen. We have posted over 27,000 stories and have received nearly 850,000 comments in the just over 5 years since SoylentNews was launched... here's looking forward to many more years to come!!


Original Submission

posted by martyb on Thursday May 23 2019, @12:30AM   Printer-friendly
from the insert-picure-of-big-haired-guy-saying-it-was-aliens.jpg dept.

We recently had reports of some 'wonkiness' on the site.

Reports started appearing in our #Soylent channel on IRC about 90 minutes ago. For example, the Main Page would load, but parts of the page (such as the slashboxes on the left-hand side) were missing.

I borked my first attempt, but on the second try successfully restarted apache and slashd on both of our front-end servers: hydrogen and fluorine.

All seems to be working correctly now. If this is not the case for you, you may need to clear the browser cache on your system and/or do a hard reload of the page (e.g. Ctrl+F5). If things are still not right, please reply in the comments and/or pop into channel #dev on IRC and let us know.

I'm not sure what precipitated the behavior; I'll leave that to TheMightyBuzzard or one of the sysadmin folk to investigate. I'm sure they'll fill us in on whatever root cause was found.

OTOH, one cannot entirely rule out a spurious gamma ray that flipped a key bit in memory that caused an avalanche of untrapped events.

You can now return to your usual, spirited discussions.


Original Submission

posted by martyb on Tuesday April 23 2019, @03:19PM   Printer-friendly
from the and-then-there-were-some dept.

We had a minor site hiccup today. All seems to be working, now.

We have always been open and upfront about the site, so in the interests of full disclosure here is a summary of the problem and steps taken to fix it.

tl;dr Comment counts shown for each story on the main page seem to have stopped getting updated since about midnight this morning; appears to be working now. Please accept our apologies for any who were inconvenienced.

Read on past the fold for details.

Problem: Comment counts on the main page showed "0" comments on recent stories, but opening a story showed the correct number of comments for it.

Actions Taken:

1.) Try bouncing the front-end servers to restart apache (This is a low-risk step that seems to fix a surprising number of issues).

No joy.

2.) Ask for help on the #dev channel on IRC.

Ncommander replied asking if slashd (an over-seeing daemon for the site) was running.

Looked through my log files and on the site wiki; determined that slashd should be running on server: fluorine

ps -AF | grep slashd | wc showed 32 processes

Ncommander suggested: killall -9 slashd

Try: killall -9 slashd

"No process found."

Inspection of output of PS -AF suggested this one-liner should do it:
$(ps -AF | grep slashd | awk '{print "kill -9 " $2}' )

Got most of the processes, but there still seemed to be some stragglers.

/etc/init.d/./slash stop
/etc/init.d/./slash restart

Conclusion:

Looked like it might have worked... reloaded main page... see updated comment counts!

Looks like all is working again.

It's a credit to the staff here that the site has been running so smoothly and without crashing or hiccups for... I can't remember when we last had an outage. Given that in the early days of the site we had maybe a few hours of uptime between crashes, we have come a long ways!

I'm going to assume this is one of those "have you tried turning it off and back on again" kind of problems, and unless the problem re-occurs, assume it is solved.

Need to hurry to get to work, so I apologize for the brevity of this posting.

--martyb


Original Submission

Today's News | July 3 | July 1  >