Running containers not detected correctly

  • Thread starter Thread starter kusman
  • Start date Start date
K

kusman

Guest
I recently recognised an issue with one of the proxmox servers where openvz containers running on the host do not get recognised by the host node. Basically, if I perform vzlist, it shows them as running, but the proxmox web interface is showing them as offline. I have upgraded to the latest version of proxmox since I detected the problem, but it did not solve the issue.

Any help with this issue would be appreciated.
 
post the output of:

> pveversion -v

and make sure that you reload the web management page.
 
The output is as follows. All the proxmox related processes were restarted yes, but this did not have any effect on the issue.

proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-20-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-26-pve: 2.6.32-114
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-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
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.1-1