bigv1-head2 blip

Expected resolution: 23 Jul 2015, 21:40 UTC
Return to issues
Issue status: Resolved Date:

23 Jul 2015
22:11 UTC

Posted by:

Bytemark Engineer

Resolved

Issue status: Investigating Date:

23 Jul 2015
21:45 UTC

Posted by:

Bytemark Engineer

bigv1-head2 issued some odd kernel messages at around 20:30 BST today, corresponding with a reboot of a subset of the BigV virtual machines it was running. The remaining VMs have been migrated away and those that were killed have all been restarted on other heads.

head24 had similar issues earlier in the day; they have similar hardware and capacity, along with similar uptime figures (~120 days). I don't know how much we can draw from that, right now.

All VMs should be back up now, anyway. If you have any problems, do raise an alert with support in the usual way.

Return to issues

Issue still not addressed? Please contact support.