[GNC-dev] [MAINT] Server Downtime to relocate hardware, Feb 1, 2020
derek at ihtfp.com
Sat Feb 1 23:59:58 EST 2020
I've got my main servers racked, network transitioned, and VM host upgraded.
I turned the VM's back on around 23:30 local time.
As you can see from this message, code is now passing mail again.
I know gncbot is also sitting in IRC.
So I'm going to call the server back up and running.
If you see any issues please let me know and I'll check it in the morning.
I do still have some work to do; the VMs didn't come up on their own and
needed some manual intervention. I know why, but I'm going to have to
track down how to work around the new issue. :( Unfortunately testing
this might require more downtime to ensure it's working.
I'll try to schedule that when I can.
For now, I'm going to try to get some rest.
On Sat, February 1, 2020 4:58 pm, Derek Atkins wrote:
> This maintenance is about to begin.
> On Fri, January 31, 2020 9:52 pm, Derek Atkins wrote:
>> Just a reminder that this is scheduled for tomorrow.
>> I am expecting the work to start around 4pm US/ET (2100 UTC).
>> I will send one more email before I start to turn down servers, and will
>> be on
>> IRC as much as I can during the work.
>> "Derek Atkins" <derek at ihtfp.com> writes:
>>> TL;DR: I plan to move the hardware that runs code.gnucash.org on the
>>> afternoon/evening of February 1, 2020, which will involve some
>>> downtime as the machine is physically moved and then racked. Expect
>>> anywhere from 4-12 hours of downtime for email, wiki, archives, gncbot,
>>> and git master. Exact time TBD; real-time updates will go to #gnucash
>>> Long version: On the afternoon of February 1, 2020 I plan to relocate
>>> hardware to its more permanent location. This will involve significant
>>> downtime because I have toL
>>> 1) shut down the systems
>>> 2) reconfigure the local network at the old location
>>> 3) reroute the IPv4 tunnel to the new location (which requires
>>> coordination with another entity)
>>> 4) physically move the machines from the old location to new location
>>> 5) install the new machines in the racks at the new location
>>> 6) reconfigure the local network for the tunnel
>>> 7) turn on an test
>>> I expect this whole process will take at least 4 hours, but probably
>>> longer depending on many variables. However, once it is complete the
>>> system will be (back) on a 1Gb fiber with a good-sized UPS for
>>> short-to-medium length power outages (which we've had none in the past
>>> I will send an email about 30 minutes before I begin, and again after
>>> project is complete. I'll remain on IRC in the interim for more
>>> During this outage, most gnucash services will be unavailable. This
>>> includes: email lists and archives, wiki, git master, IRC gncbot,
>>> services, etc. The web site, www.gnucash.org, will remain available
>>> will post a news article about the maintenance.
>>> DEVS: Please let me know ASAP if there are specific time frames that
>>> would adversely affect you. I do have some flexibility in doing this
>>> Please let me know if you have any questions, comments, or concerns
>>> to this work.
>> Derek Atkins 617-623-3745
>> derek at ihtfp.com www.ihtfp.com
>> Computer and Internet Security Consultant
>> gnucash-devel mailing list
>> gnucash-devel at gnucash.org
> Derek Atkins 617-623-3745
> derek at ihtfp.com www.ihtfp.com
> Computer and Internet Security Consultant
Derek Atkins 617-623-3745
derek at ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
More information about the gnucash-devel