vz4 being slow - All VMs moved

Stephen

US Operations
Staff member
We are checking Vz4, it is being very slow to load, there is large cpu usage, but it is not showing why.

We are working to correct this.
 
Re: vz4 being slow

This is one of the oddest issues ever, the VPSes start up, and within moments cpu usage goes to 85% and hangs up everything, we suspect a CPU disk drive may have some issue and causing this, but it is making the server non responsive.
 
Re: vz4 being slow

We are going to make it such that no VM starts on reboot, apply updates and reboot, then start the VMs one by one to isolate the issue.
 
Re: vz4 being slow

Updates all run, a while back, all but 2 VPSes up now, and working to bring them up as well.
 
Re: vz4 being slow

The VPS responsible for issues, has been found! Started it up and within 30 seconds the entire node was crawling slow. working to stop it, and find what is going on with it!
 
Re: vz4 being slow

Whew, we managed to get it STOPPED and prevent having another reboot.
 
Re: vz4 being slow

:( With the win6 and win9 issue that came, I did not email the staff with the ID making problems, so that VM got started on a ticket request, and it has caused problems again, we are working to get in control, and it will be shared with all staff to be sure this doesn't happen again.
 
Re: vz4 being slow

All issues, except the one VPS that was harming all, resolved now.
The one VPS is having its own node setup to run tests now, in a place it can't kill other servers.
 
Re: vz4 being slow - resolved

Sometimes automation software kicks you in the rear, we moved this VM and we needed to edit the config, it edited and started the VM on the vz4 server instead of the new isolated one it is set to now.

Working to resolve!
 
Re: vz4 being slow - resolved

and after reboot, the virtuozzo main service failed to start :(

At this point I have to point out this is why we are pushing Hyper-V as the main virtual service now, it is far more stable and less issues like this.
 
Re: vz4 being slow - resolved

This is not looking too good at the moment, the virtuozzo service is not starting, which means no VM starts.

We have backups of all environments, so restoring is an option but we have to do to another node, and migration isn't functional due to the service not coming up. We are working to migrate these VMs as quickly as possibly manually.
 
Re: vz4 being slow - again some problems

We have all but one client VM migrated to another node, the others are only internal testing and we will move them at our own pace :)
 
Back
Top