Hello fellow Soylentils!
[Update:] We survived all three days of reboots without major issues. Many thanks to all who prepped the systems, prodded things along, and were on standby to deal with any unforeseen issues!
We were informed by Linode (our hosting provider) that they needed to perform some maintenance on their servers. This forces a reboot of our virtual servers which may cause the site (and other services) to be temporarily unavailable.
Here is the three-day reboot schedule along with what runs on each server:
Status | Day | Date | Time | Server | Affects |
---|---|---|---|---|---|
Done | Tues | 2015-10-20 | 0200 UTC | boron | DNS, Hesoid, Kerberos, Staff Slash |
Done | Tues | 2015-10-20 | 0500 UTC | beryllium | IRC, MySQL, Postfix, Mailman, Yourls |
Done | Wed | 2015-10-21 | 0500 UTC | sodium | Primary Load Balancer |
Done | Wed | 2015-10-21 | 0500 UTC | magnesium | Backup Load Balancer |
Done | Wed | 2015-10-21 | 0700 UTC | neon | Production Back End, MySQL NDB cluster |
Done | Thu | 2015-10-22 | 0200 UTC | hydrogen | Production Front End, Varnish, MySQL, Apache, Sphinx |
Done | Thu | 2015-10-22 | 0500 UTC | helium | Production Back End, MySQL NDB, DNS, Hesoid, Kerberos |
Done | Thu | 2015-10-22 | 0900 UTC | fluorine | Production Front End, slashd, Varnish, MySQL, Apache, ipnd |
Done | Thu | 2015-10-22 | 1000 UTC | lithium | Development Server, slashd, Varnish, MySQL, Apache |
We apologize in advance for any inconvenience and appreciate your understanding as we try and get things up and running following each reboot.
(Score: 2) by sjames on Tuesday October 20 2015, @11:24PM
Same physical server?
(Score: 2) by NCommander on Wednesday October 21 2015, @12:22AM
Probably. Linode doesn't let us see the physical node they're both on, which is a problem when they reboot them.
Still always moving