Cluster Nodes become red without any reason once a week

[tom]

no, the iso does never include latest version, just read your own link.

 

[mschultz]

Our installation was complete 6 weeks ago -- very recent. Here is the pve version:

pve-manager: 2.2-24 (pve-manager/2.2/7f9cfa4c)
running kernel: 2.6.32-16-pve
proxmox-ve-2.6.32: 2.2-80
pve-kernel-2.6.32-16-pve: 2.6.32-80
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-1
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-28
qemu-server: 2.0-62
pve-firmware: 1.0-21
libpve-common-perl: 1.0-36
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-34
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.2-7
ksm-control-daemon: 1.1-1

 

[tom]

No, your version is old. The bug is fixed so I don't understand why you do not install it . . .

 

[ppo]

after update:
root@proxmox:~# 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-16-pve: 2.6.32-82
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-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-72
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

Thanks for help

 

[tom]

looks ok.

 

[mschultz]

Thank you, Tom.

The Proxmox web console doesn't seem to have a notification when a newer version is available for upgrade. What is the recommended way to stay on top of code releases? Should I check your web site once in a while, or is there a better (automated?) process for doing this?

Best,

Mark

you run the old version with the bug, just upgrade and your issue will be fixed.

see http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.2

 

[mschultz]

oh, I suppose I just check for debian updates (the sources.list file is correct) and I will know. if there is an even easier way though, appreciate it... otherwise, no need to publish the previous comment. thank you.

you run the old version with the bug, just upgrade and your issue will be fixed.

see http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.2

 

[Marvin]

Perhaps running: apt-get -V -s dist-upgrade