Hi,
one of our ProxMox Servers freezes when the daily backup starts at night. The Problem occurs only since I have upgraded him last week from 2.3 to 3.0.
The backups were stored on a nfs server, but others PM Servers have no problems with there backups on this nfs server running without a problem, despite they are also upgraded from 2.3 to 3.0.
When the problem server "freezes" the webinterface is online but you can´t stop openvz vms and all vms are displayed as offline and without there names. The Server also does not react at the reboot command per ssh, it seems he try to shutdown the vms but hangs there with no reaction. The vms are still ping able but there services as http or smtp are not working.
Have any one a similar problem since the upgrade to 3.0?
Here is the output of pveversion on our problem server:
pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
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-4
qemu-server: 3.0-20
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1
Greetings,
Marcel
one of our ProxMox Servers freezes when the daily backup starts at night. The Problem occurs only since I have upgraded him last week from 2.3 to 3.0.
The backups were stored on a nfs server, but others PM Servers have no problems with there backups on this nfs server running without a problem, despite they are also upgraded from 2.3 to 3.0.
When the problem server "freezes" the webinterface is online but you can´t stop openvz vms and all vms are displayed as offline and without there names. The Server also does not react at the reboot command per ssh, it seems he try to shutdown the vms but hangs there with no reaction. The vms are still ping able but there services as http or smtp are not working.
Have any one a similar problem since the upgrade to 3.0?
Here is the output of pveversion on our problem server:
pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
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-4
qemu-server: 3.0-20
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1
Greetings,
Marcel