Hi chaps,
This has been on ongoing problem for some time and I can't seem to find the fix.
We have a 4 host cluster running 2.2/2.3. One of my hosts only runs one VM (an Oracle DB on RHEL 5 update 7) which occasionally for no particular reason shuts itself off. I "think" it may be something to do with the Network card but have tried it with both e1000 and virtio NIC's - virtio seems to last a bit longer (around 6 or 7 days), but e1000 never gets past 48 hours.
I've been monitoring with atop and am seeing very high usage on the VM network entry (tap170 in my case), sometimes as high as 500%.
I am also seeing lots of lots of entries like this in the syslog around the time of the failures:
Mar 26 09:34:21 ess-prox-009 corosync[2110]: [TOTEM ] Retransmit List: 1b19b4 1b198f 1b1990 1b1991 1b1992 1b1993
1b1994 1b1995 1b1996 1b1997 1b1998 1b1999 1b199a 1b199b 1b199c 1b19b2 1b19b3 1b19b6
Not sure if this is just coincidence though.
This is my pveversion for the host in question:
root@ess-prox-009:~# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-93
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-19-pve: 2.6.32-93
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
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-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1
Any help much appreciated and would be interested if anyone else has had this problem.
Cheers,
c
This has been on ongoing problem for some time and I can't seem to find the fix.
We have a 4 host cluster running 2.2/2.3. One of my hosts only runs one VM (an Oracle DB on RHEL 5 update 7) which occasionally for no particular reason shuts itself off. I "think" it may be something to do with the Network card but have tried it with both e1000 and virtio NIC's - virtio seems to last a bit longer (around 6 or 7 days), but e1000 never gets past 48 hours.
I've been monitoring with atop and am seeing very high usage on the VM network entry (tap170 in my case), sometimes as high as 500%.
I am also seeing lots of lots of entries like this in the syslog around the time of the failures:
Mar 26 09:34:21 ess-prox-009 corosync[2110]: [TOTEM ] Retransmit List: 1b19b4 1b198f 1b1990 1b1991 1b1992 1b1993
1b1994 1b1995 1b1996 1b1997 1b1998 1b1999 1b199a 1b199b 1b199c 1b19b2 1b19b3 1b19b6
Not sure if this is just coincidence though.
This is my pveversion for the host in question:
root@ess-prox-009:~# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-93
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-19-pve: 2.6.32-93
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
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-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1
Any help much appreciated and would be interested if anyone else has had this problem.
Cheers,
c