XEN24 Node
-
Monday, 2nd March, 2015
-
19:47pm
7.47pm: We are aware our XEN24 Node has become unresponsive. A reboot has not brought the server back on line. We have requested a KVM session for this server and we will update you once we have access and have diagnosed the issue. We are sorry for this issue. This is a node that was first deployed in October 2014 and has had 100% uptime until this evening.
8.07pm: We see an error on KVM ' " usb 2-1.1 device not accepting address 32 " - we need to enlist the help of the data centre remote hands to reseat the KVM cable and network cable as the kvm keyboard is not accepting commands. Apologies for the extended delay on being able to diagnose this.
8.40pm: We have had the cables re-seated and now can access the server. We are beginning our work to determine the issue. Updates as soon as we have them.
9.00pm: Unfortunately the reboot is hanging (we tried twice) we need to get the data centre remote hands again to assist with a physical reboot on the server itself and checking the ethernet cable. We're sorry about this and will update you as soon as we have some more information.
9.49pm: We apologise for the delay the data centre technicians have responded and are working on the server now. We will have some information soon
10.02pm: The remote hands have manually intervened and the server rebooted. We apologise for the delay which was extended by (1) Initial KVM not working and the USB cable needing re-seated and (2) 49 minutes for a remote hands request to be actioned for a manual reboot and replacement of the ethernet cable.
We are closing this issue now and if you need any more clarification please do not hesitate in opening a ticket.
