OpenVZ: Restore problem

[tdo]

Hello,

I have a problem with starting a restored openvz machine. I've just installed a new machine (second) with proxmox 2.1 (pve-manager/2.1/f9b0f63a) and I have another (first) system with proxmox 2.1 (pve-manager/2.1/f9b0f63a).

When I create a backup of a container on the first machine and restoring it on the new second system and then starting the container, I get this error message in the webinterface:

Starting container ...
Container is mounted
Container start failed (try to check kernel messages, e.g. "dmesg | tail")
Container is unmounted
TASK ERROR: command 'vzctl start 999' failed: exit code 7

~# dmesg | tail
warning: `vzctl' uses 32-bit capabilities (legacy support in use)
Failed to initialize the ICMP6 control socket (err -105).
CT: 999: stopped
CT: 999: failed to start with err=-105
Failed to initialize the ICMP6 control socket (err -105).
CT: 999: stopped
CT: 999: failed to start with err=-105
Failed to initialize the ICMP6 control socket (err -105).
CT: 999: stopped
CT: 999: failed to start with err=-105

How do I solve this issue? The second system has different hardware specifications. I've also tried to restore the same container on the same system (first) to a new id. This works without problems. So, something must be wrong on the new (second) system.

pveversion -v (first):

pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-15
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

pveversion -v (second, new):

pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-15
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

 

[tdo]

Okay, I think I have solved this problem. I have commented the "numothersock" in the config file. Now the container starts fine.
Edit: Increasing the value also helps. Old value for my container was "100:100" I've changed it to "200:200" and it works.

 

[Behnoosh Nushi]

thanks, can you tell me what value you are talking about?

 

[Behnoosh Nushi]

Sorry what config file and what value you are talking?

 

[tdo]

I was talking about the "numothersock" value in the config file of the OpenVZ container (/etc/pve/openvz/<ID>.conf)

 

[Behnoosh Nushi]

SO you mean outside the stopped CT right? Because I cannot enter to the CT to check the config file so you mean outsid ethe ubuntu ct and I have to go to the Proxmox Shell to change it? When I go to the path you gave me, it says no such a file or directory

I was talking about the "numothersock" value in the config file of the OpenVZ container (/etc/pve/openvz/<ID>.conf)

 

[tdo]

Yes, outside the CT (and inside proxmox host system). Normally there should be your config files in /etc/pve/openvz/ with the VM IDs (e.g. /etc/pve/openvz/100.conf). Check the directory.

 

[Behnoosh Nushi]

OH Ok I got it. I found the conf file and commented numothersock ( there was no number in front of it see the attached PICs plz) but again It is not running it gets stopped
see these screenshots:

Yes, outside the CT (and inside proxmox host system). Normally there should be your config files in /etc/pve/openvz/ with the VM IDs (e.g. /etc/pve/openvz/100.conf). Check the directory.