gpg: Signature made Wed Nov 26 15:27:09 2014 UTC
gpg: using DSA key 2099B64CBF15490B
gpg: Good signature from "Andy Smith <andy@strugglers.net>" [unknown]
gpg: aka "Andrew James Smith <andy@strugglers.net>" [unknown]
gpg: aka "Andy Smith (UKUUG) <andy.smith@ukuug.org>" [unknown]
gpg: aka "Andy Smith (BitFolk Ltd.) <andy@bitfolk.com>" [unknown]
gpg: aka "Andy Smith (Linux User Groups UK) <andy@lug.org.uk>" [unknown]
gpg: aka "Andy Smith (Cernio Technology Cooperative) <andy.smith@cernio.com>" [unknown]
Hi,
Around 1432Z IPv6 connectivity to all hosts was lost, and VPSes on
kwak.bitfolk.com became unreachable (both IPv4 and v6).
Subsequent investigation has revealed that kwak.bitfolk.com was
unexpectedly power cycled and returned in a configuration that had
no networking.
IPv6 connectivity was restored at around 1503Z and VPSes hosted on
kwak.bitfolk.com are now in the process of being booted again.
If you are unable to reach your VPS, and it is hosted on
kwak.bitfolk.com¹, please log in to your Xen Shell and look at its
console to see what is happening:
https://tools.bitfolk.com/wiki/Xen_Shell
There is a high possibility that the VPS is still booting, is
performing a filesystem check, or has failed to boot because of some
configuration problem local to your VPS.
If you have ruled all of those out then please do send a support
ticket to support@???. For those of you with Nagios
monitoring set up I will be watching to make sure any alerts
recover where that is within my power.
To follow:
- How kwak came to be power cycled
- Why it didn't boot with networking enabled
- Why IPv6 broke for everyone even though it should have failed over
to another router.
Cheers,
Andy
¹ If you don't know, you can find out which piece of hardware your
VPS is hosted on as follows:
https://bitfolk.com/customer_information.html#toc_3_Which_piece_of_actual_hardware_is_my_VPS_hosted_on_
--
http://bitfolk.com/ -- No-nonsense VPS hosting
Please consider the environment before reading this e-mail.
— John Levine
