OpenVZ Forum

Home » General » Support » Getting error when trying to restart VMs
Getting error when trying to restart VMs [message #50033] Tue, 23 July 2013 22:18 Go to previous message
nolageek is currently offline  nolageek
Messages: 4
Registered: July 2013
Location: United States
Junior Member
While I don't know if it's related to r1soft, we're having an issue on openvz (using openvz web panel) after installing r1soft agent.

We are not able to restart or start any of the VMs without getting an popup error "Cannot change the virtual server state" and the error in the log is:

Jul 23 10:29:23 vz kernel: [370670.831802] CT: 5: stopped
Jul 23 10:29:23 vz kernel: [370670.832026] CT: 5: failed to start with err=-12

When starting the VM and creating a debug.log this seems to be the relevant part:

840074 ioctl(4, 0x40202e0a, 0x7fff63c36900) = -1 ENOMEM (Cannot allocate memory)
840074 write(2, "env_create error", 16) = -1 EBADF (Bad file descriptor)
840074 write(2, ": Cannot allocate memory", 24) = -1 EBADF (Bad file descriptor)
840074 write(2, "\n", 1) = -1 EBADF (Bad file descriptor)

R1Soft stopped the agent service and unloaded the hcpdriver that we use to perform backups. Afterwards, they attempted to run a simple list of the current running vznodes on the server and notice that it's returning "Cannot allocate memory" error messages.

[root@vz ~]# vzlist
Can't access file /vz/private/7/root.hdd/DiskDescriptor.xml: Cannot allocate memory
Can't access file /vz/private/8/root.hdd/DiskDescriptor.xml: Cannot allocate memory
2 70 running xx4.1xx.x3.204
4 72 running 1xx.xx4.2x.206
6 19 running 1xx.1x.x3x.205
7 68 running xx.x4.1xx.98
8 66 running xx.154.1x9.x9
10 58 running xxx.xx.1x9.1xx

R1Soft says the problem doesn't look to be related to the cdp-agent process nor the driver as this issue wouldn't be a problem after stopping and unloading the driver. There is plenty of memory on the server so not sure why the cannot allocate memory is being returned. If this continues to be an issue we can uninstall the agent entirely to see if it makes a difference, but based on what I can find the agent installation is not the cause of this issue.

Any suggestions?
Read Message
Read Message
Previous Topic: kernel-firmware-2.6.32-358.14.1.el6.noarch is obsoleted by vzkernel-firmware-2.6.32-042stab078.28
Next Topic: how to migrate x86 container from x86 to x86_64
Goto Forum:

Current Time: Tue Jul 23 02:24:20 GMT 2024

Total time taken to generate the page: 0.02238 seconds