BigV1 Head24 Reboot (again)

Expected resolution: 13 May 2016, 08:00 UTC
Return to issues
Issue status: Resolved Date:

13 May 2016
08:11 UTC

Posted by:

Ian Chilton

Machines have been moved off head24. Apologies to those who have had problems. Our DC team will be taking this hardware offline for investigation and diagnostics.

Issue status: Investigating Date:

13 May 2016
07:48 UTC

Posted by:

James Hannah

We've now moved most of the machines off this hardware (hopefully you shouldn't have noticed this), and the rest will be completed shortly.

Issue status: Investigating Date:

13 May 2016
02:33 UTC

Posted by:

James Hannah

Obviously we didn't expect this to happen twice, especially not exactly 24 hours after the first incident as last night's failure appeared to be a random occurrence, this now doesn't appear to be the case.

Our team will look into getting machines migrated off this head tonight so that the same thing doesn't happen tomorrow.

Issue status: Investigating Date:

13 May 2016
02:28 UTC

Posted by:

James Hannah

Somehow, the same BigV "head" that failed last night has done the same thing exactly 24 hours later, this is rather unprecedented.

The head has already been rebooted and machines will be starting up, if yours doesn't come up quickly enough then you can trigger a restart via the panel, although waiting will do the same thing eventually.

Return to issues

Issue still not addressed? Please contact support.