Hi.
I'm trying to create a new container in my Proxmox 3.1-3 environment, but I'm continuously having the following error:
The id of the new container is 1002, of course, but I tried with other numbers too (110 for example), and I got the same error.
The /var/lib/vz/private directory exists and /var/lib/vz has 500G of space available.
I also tried to restart the server without solving the problem.
This is my pveversion:
Could you help me, please?
Thank you very much.
Bye.
I'm trying to create a new container in my Proxmox 3.1-3 environment, but I'm continuously having the following error:
Code:
Error: can't lock container 1002The /var/lib/vz/private directory exists and /var/lib/vz has 500G of space available.
I also tried to restart the server without solving the problem.
This is my pveversion:
Code:
root@pve /var/lib/vz # pveversion -v
proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve)
pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-7
qemu-server: 3.1-1
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-10
pve-libspice-server1: 0.12.4-1
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2Thank you very much.
Bye.