[Update 5: All done. Nuttin but net. --TMB]
[Update 4: As of 20180509 @ 11:55 UTC, beryllium has been successfully rebooted. This leaves hydrogen to be rebooted in just over 13 hours. --martyb]
[Update 3: As of 20180509 @ 0414 UTC, both lithium and sodium appear to have successfully completed their reboots. That leaves beryllium (1hr45m from now) and hydrogen (20h45m from now) to complete their reboots. --martyb]
[Update 2: The second round of reboots went peachy keen as well. Next round starts at 3AM UTC (7 hours from this story's time) with our dev server (lithium). An hour later the load balancer (sodium) that I switched us off of this morning will reboot. Two hours after that the box (beryllium) that hosts the wiki, mail, IRC, and some other lesser-used stuff will get bounced. If you can't stand being disconnected from IRC for a few minutes, add irc2.sylnt.us (6667/6697) to the list of servers for this network. --TMB]
[Update 1: The first scheduled reboot (of fluorine) was successful. The two-hour reboot window for helium starts 1.5 hours from the date/time stamp for this story. Two hours after that marks the commencement of the two-hour reboot window for boron, magnesium, and neon. We do not anticipate any site interruption as a result of these reboots. --martyb]
We have been informed by Linode (on which all of the SoylentNews servers are hosted) that maintenance is required to mitigate against the Spectre (v1 and v2) attacks. As a result, all of our servers will require a reboot. Historically, any given server is down for anywhere from 15-30 minutes. We have redundancies in place for many of our operations, but there may be some unavoidable downtime. We ask your patience and understanding during this process.
The scheduled reboots are:
Sat | 2018-05-05 1:00:00 AM UTC | fluorine [1] | Production Cluster | Completed |
Tue | 2018-05-08 1:00:00 AM UTC | helium | Production Cluster | Completed |
Tue | 2018-05-08 3:00:00 AM UTC | boron | Services Cluster | Completed |
Tue | 2018-05-08 3:00:00 AM UTC | magnesium | Frontend Proxy | Completed |
Tue | 2018-05-08 3:00:00 AM UTC | neon | Production Cluster | Completed |
Wed | 2018-05-09 3:00:00 AM UTC | lithium | Development Cluster | Completed |
Wed | 2018-05-09 4:00:00 AM UTC | sodium | Frontend Proxy | Completed |
Wed | 2018-05-09 6:00:00 AM UTC | beryllium [2] | Services Cluster | Completed |
Thu | 2018-05-10 1:00:00 AM UTC | hydrogen | Production Cluster | Completed |
[1] Unable to process subscriptions or update comment counts or deliver messages until it reboots.
[2] IRC (Internet Relay Chat) server will be unavailable.
(Score: 4, Informative) by martyb on Thursday May 03 2018, @02:08PM (8 children)
First off, I also find the server names confusing.
But, I would point out that there is a reason to divorce the name of the server from its use. A few years back, in an effort to reduce servers costs, several services were migrated between servers. The end result was that we required fewer servers to run the site. (Save money, yay!) Had we followed the suggested naming scheme, and had a server named "fe001", (Front End 001) what do you call it when the IRC services are migrated to it? Some of our servers support multiple, "namable" services... which name to choose for it?
Though less than self-evident to the casual observer, having servers named this way does serve a purpose.
I added a column to the reboot schedule with what I could quickly find as to each server's purpose. Am pressed for time or else I could investigate more and provide a more detailed enumeration of what services run where.
Wit is intellect, dancing.
(Score: 1) by mechanicjay on Monday May 07 2018, @11:35PM (6 children)
My VMS box beat up your Windows box.
(Score: 5, Insightful) by The Mighty Buzzard on Monday May 07 2018, @11:41PM (4 children)
Agreed. We should have went with Star Trek ship names.
My rights don't end where your fear begins.
(Score: 2) by bob_super on Monday May 07 2018, @11:51PM (3 children)
Are you actually ready to handle all the terrible quotes that would follow any mishap ?
It's one thing to spend a whole night fixing a broken dependency somewhere after a security update, and another to subsequently refrain from killing the geeks telling you that you should have just inverted the polarity on your di-lithium crystals when your shields went down.
(Score: 2) by The Mighty Buzzard on Tuesday May 08 2018, @12:36AM (1 child)
Nah, some jokes just don't get old, they just become running gags.
My rights don't end where your fear begins.
(Score: 1, Funny) by Anonymous Coward on Tuesday May 08 2018, @10:27PM
In Soviet Russia gags run you da comrade?
(Score: 2) by Gaaark on Wednesday May 09 2018, @04:40AM
The Buzzard canna handle mooch more of this, Captain!
--- Please remind me if I haven't been civil to you: I'm channeling MDC. ---Gaaark 2.0 ---
(Score: 2) by RS3 on Wednesday May 09 2018, @12:40AM
This has been an interesting discussion for me because I don't think I would care, but it's interesting in that you've all pointed out that it can be a distraction, add an unnecessary layer of nomenclature, confusion, etc. My first ISP, ca. 1994, had servers names "renoir, monet, manet, matisse, degas, ..." Being I like art, I thought it was kind of cool, and I knew what was running on what. I'm pretty boring with server names where it's up to me.
(Score: 2, Informative) by pTamok on Tuesday May 08 2018, @09:22PM
Right in the button, server names should definitely bear no relation to their function. That way lies madness.
As ever, a big thank-you to the maintainers and editors of this site.