Can't create new container

[axion.joey]

Hi,

We have a 2-node Proxmox Cluster. And for some reason we cannot create new containers on the second node. When we try we receive the following error message: unable to open file '/etc/pve/nodes/proxmoxla2/openvz/338.conf.tmp.984621' - Device or resource busy.

I also cannot write any files to /etc/pve/nodes/proxmoxla2/openvz/.

Thanks in advance for your help

Here are the details on the two nodes
Node 1

pvecm status
Version: 6.2.0
Config Version: 2
Cluster Name: LACluster
Cluster Id: 39092
Cluster Member: Yes
Cluster Generation: 336
Membership state: Cluster-Member
Nodes: 2
Expected votes: 2
Total votes: 2
Node votes: 1
Quorum: 2
Active subsystems: 5
Flags:
Ports Bound: 0
Node name: proxmoxla1
Node ID: 1
Multicast addresses: 239.192.152.77
Node addresses: 172.16.1.20

pvecm nodes
Node Sts Inc Joined Name
1 M 300 2013-03-17 12:53:23 proxmoxla1
2 M 336 2013-05-13 14:37:50 proxmoxla2


/etc/pve/cluster.conf
<?xml version="1.0"?>
<cluster name="LACluster" config_version="2">


<cman keyfile="/var/lib/pve-cluster/corosync.authkey">
</cman>


<clusternodes>
<clusternode name="proxmoxla1" votes="1" nodeid="1"/>
<clusternode name="proxmoxla2" votes="1" nodeid="2"/></clusternodes>


</cluster>


pveversion -v
pve-manager: 2.2-32 (pve-manager/2.2/3089a616)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-17-pve: 2.6.32-83
pve-kernel-2.6.32-16-pve: 2.6.32-82
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-71
pve-firmware: 1.0-21
libpve-common-perl: 1.0-41
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-10
ksm-control-daemon: 1.1-1

Node 2
pvecm status
Version: 6.2.0
Config Version: 2
Cluster Name: LACluster
Cluster Id: 39092
Cluster Member: Yes
Cluster Generation: 336
Membership state: Cluster-Member
Nodes: 2
Expected votes: 2
Total votes: 2
Node votes: 1
Quorum: 2
Active subsystems: 5
Flags:
Ports Bound: 0
Node name: proxmoxla2
Node ID: 2
Multicast addresses: 239.192.152.77
Node addresses: 172.16.1.21



pvecm nodes
Node Sts Inc Joined Name
1 M 336 2013-05-13 14:37:50 proxmoxla1
2 M 332 2013-05-13 14:37:50 proxmoxla2

/etc/pve/cluster.conf
<?xml version="1.0"?>
<cluster name="LACluster" config_version="2">


<cman keyfile="/var/lib/pve-cluster/corosync.authkey">
</cman>


<clusternodes>
<clusternode name="proxmoxla1" votes="1" nodeid="1"/>
<clusternode name="proxmoxla2" votes="1" nodeid="2"/></clusternodes>


</cluster>



pveversion -v
pve-manager: 2.2-32 (pve-manager/2.2/3089a616)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-17-pve: 2.6.32-83
pve-kernel-2.6.32-16-pve: 2.6.32-82
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-71
pve-firmware: 1.0-21
libpve-common-perl: 1.0-41
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-10
ksm-control-daemon: 1.1-1

 

[dietmar]

Does it help if you restart the 'pve-cluster' service (and maybe 'pvedaemon' and 'pveproxy' afterwards)

 

[axion.joey]

Does it help if you restart the 'pve-cluster' service (and maybe 'pvedaemon' and 'pveproxy' afterwards)

service pve-cluster restart worked perfectly. Should I still restart pvedaemon and pveproxy?

 

[dietmar]

service pve-cluster restart worked perfectly. Should I still restart pvedaemon and pveproxy?

Not needed if the GUI works as expected.

 

[axion.joey]

Thanks so much. I truly appreciate you help.

 

[axion.joey]

This continues to happen intermittently. Are there any steps we can do to try and determine the root cause so we can put a permanent fix in place?

 

[tom]

This continues to happen intermittently. Are there any steps we can do to try and determine the root cause so we can put a permanent fix in place?

2.2 is very outdated, upgrade to current stable (3.1) and if you see still the issue, come back here.

 

[axion.joey]

2.2 is very outdated, upgrade to current stable (3.1) and if you see still the issue, come back here.

Will do I'll also see if I can get approval for a support subscription. Question regarding that. we have a total for 24 proxmox servers, but only 4 are in production. Can we get support subscriptions for only the four production servers?

 

[tom]

please contact our sales team via office@proxmox.com for all subscription questions.