[57north-discuss] Fwd: Your BitFolk VPSes ("garioch", "finzean") need to be rebooted for critical maintenance
rmcw at allmail.net
Sat Feb 23 13:14:02 GMT 2019
Servers are going to be rebooted for Xen updates in early hours of next Sunday.
I have also just installed updates that include kernel updates for the guests so they'll be picked up with those reboots and there is a bit more chance of problems this time than with previous reboots.
I will try to remember to check on things Sunday morning. If you notice anything not working then (or any other time): say here. Or if this list is on the list of things not working: try IRC, or email me directly, or pester one of the directors to fix it, or I'm sure you can come up with some other ideas for how to proceed (that may, or may not, be any help in getting problems fixed).
Robert McWilliam rmcw at allmail.net argh.technology
Long periods of drought are always followed by rain.
----- Original message -----
From: andy at bitfolk.com
To: Robert McWilliam <rmcw at allmail.net>
Subject: Your BitFolk VPSes ("garioch", "finzean") need to be rebooted for critical maintenance
Date: Saturday, 23 February 2019 10:12
We've recently been made aware of some serious security issues in the
hypervisor software that we use (Xen). Fixing these problems will
require us to reboot our hosts and therefore all customer VPSes must
also be rebooted (or experience suspend/restore - see below).
You do not need to respond to this email unless you have questions about
We must apply these fixes to ensure the security and reliability both of
your VPSes and of our infrastructure, which is why we have no choice but
to proceed with this work in the short period of time between
notification and the end of the embargo.
I understand that this will prove disruptive to you and that you would
prefer much more notice. In better circumstances we do provide more
notice and allow for deferrals or moving VPSes between hosts, but the
seriousness of this issue means that we need to reboot everything before
the embargo on the details ends (12:00Z 5 March 2019).
Your VPSes have been assigned a maintenance window during which the
reboots will take place. The start of the maintenance window for each of
your VPSes is listed below, in UTC time zone. Each maintenance window is
up to 60 minutes long, though the work should be completed much sooner
than this, typically within a few minutes (yay, SSDs!).
| Name | Main IPv4 | Window start (UTC) |
| garioch | 126.96.36.199 | 2019-03-03 01:30 |
| finzean | 188.8.131.52 | 2019-03-03 00:30 |
At some point in each maintenance window your VPS will be cleanly shut
down. The host it is on will then be patched and rebooted, and then your
VPS will be brought up again.
You should ensure that your VPS and all its services start up correctly
on boot. We offer a free monitoring service which can help you to know
if your VPS and its services are working correctly. If you have not done
so already then you may want to get in touch with us to have this set
up. You can do that by replying to this email and describing which
services you would like monitored.
If you would prefer for us to attempt to suspend and restore your VPS
to/from storage, resulting in less disruption, then you can indicate
that preference on our web panel at:
Doing so will cause us to add ping checks for your VPS so we can have a
good chance at knowing if the restore was successful.
If you have any questions please reply to this email, which will open a
support ticket. Please note however that we cannot change the date or
time of the planned maintenance. There is no need to reply to this email
unless you have further questions, or wish to request monitoring.
More information about the 57north-discuss