Results tagged “hardware node problems” from Blacknight Hosting Network Status

pemvzwin02 hardware node having some difficulty

TrackBacks (0) Comments (0)
The above named hardware node is currently not functioning correctly. We've already initiated a reboot of it and the VPS should be back up in 15-20 minutes.

To rectify this issue, we'll be moving the VPS off of this node over the coming 24 hours and we'll then investigate these issues further without affecting Customers.

We'll post an update shortly.

Update: 16:15

This Node is now back online and 80% of the VPS, are started. The remaining 20% should be started in the next 10 or so minutes.

Emergency maintenance on a Windows Virtuozzo hardware node

TrackBacks (0) Comments (0)
Summary: Windows node pemvzwin02 is experiencing issues with internal virtuzzo API calls. This is causing a task backlog in our provisioning system. In order to diagnose the issue further we've been asked to reboot the node.

We're taking the opertunity to run windows updates while we do this, so at least some good will come of it.

The following list of VPSs are affected:

vps-238.cp.blacknight.com, vps-258.cp.blacknight.com, vps-262.cp.blacknight.com, vps-265.cp.blacknight.com, vps-271.blacknight.com, vps-282.cp.blacknight.com, vps-287.cp.blacknight.com, vps-288.cp.blacknight.com, vps-302.cp.blacknight.com, vps-317.cp.blacknight.com, vps-331.cp.blacknight.com, vps-337.cp.blacknight.com, vps-341.cp.blacknight.com, vps-342.cp.blacknight.com, vps-343.cp.blacknight.com, vps-344.cp.blacknight.com, vps-346.cp.blacknight.com, vps-347.blacknight.com, vps-353.cp.blacknight.com, vps-354.cp.blacknight.com, vps-355.cp.blacknight.com, vps-357.cp.blacknight.com, vps-361.blacknight.com, vps-362.cp.blacknight.com, vps-386.cp.blacknight.com, vps-387.cp.blacknight.com, vps-390.cp.blacknight.com, vps-407.cp.blacknight.com, vps-409.cp.blacknight.com, vps-410.cp.blacknight.com,
vps-584.cp.blacknight.com, vps-589.cp.blacknight.com, vps-612.cp.blacknight.com, vps-620.cp.blacknight.com, vps-626.cp.blacknight.com, vps-635.cp.blacknight.com, vps-642.cp.blacknight.com, vps-645.cp.blacknight.com, vps-664.cp.blacknight.com, vps-667.cp.blacknight.com, vps-672.cp.blacknight.com, vps-684.cp.blacknight.com, vps-689.cp.blacknight.com, vps-704.cp.blacknight.com, vps-709.cp.blacknight.com,
vps-710.cp.blacknight.com, vps-716.cp.blacknight.com, vps-718.cp.blacknight.com, test.zerotouch.ie

I'll update this ticket once it comes back up and all VPSs are back up. It'll probably take upto an hour, but it's completely necessary.

Update: 21:30

The node rebooted successfully and about 70% of the VPSs have restarted. The rest should be back online in the next 10 to 15 minutes or so.

We're continuing our investigation of the issues we've been encountering in our backend systems.

Recent Entries

PEMVZWIN12 Emergency Reboot
Internet Explorer is displaying issues on VPSs due to an upgrade that was performed on the hardware node. To resolve… [read more]
.be Registry Issues Last Night
We have been informed that the .be registry had some issues with their EPP server last night / this morning.… [read more]
Legacy Shared Windows server - dinadan
This server is currently experiencing difficulties serving HTTP traffic.   We are aware of the issue, and hope to have… [read more]