Bug in cluster wiev. Proxmox 2.3-13

[TrollTech]

Hi,
Have a trouble with greed tree on cluster. On two simple screenshots:
1 server:

2 server:

All vm's works and if i click to show summary status will be running. Can't reboot cluster to try fix this bug =(
Any help?

Thanks.

 

[dietmar]

Maybe a restart of the 'pvestatd' on the affected node helps?

# service pvestatd restart

 

[TrollTech]

Cant find daemon pvestatd on both servers.
---
Proxmox Virtual Environment
Version: 2.3-13/7946f1f1

 

[tom]

you need to run command on the command-line, e.g. on the server console or if via ssh.

 

[TrollTech]

# service pvestatd restart
-bash: service: command not found

# /etc/init.d/pve
pvebanner pvedaemon pvemirror pvenetcommit pvetunnel

Thanks.

 

[tom]

post the output of 'pveversion -v'

 

[TrollTech]

# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-1
pve-kernel-2.6.32-6-pve: 2.6.32-55+ovzfix-1
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6

 

[tom]

sorry, but you are totally confused.

the screenshot shows a 2.x version, also in the thread subject you talk about 2.3.

but pveversion -v shows that you use 1.9. seems you log into the wrong server.

 

[TrollTech]

Yep my fail, Sorry.

# 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-95
pve-kernel-2.6.32-19-pve: 2.6.32-95
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-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1

But restarting pvestatd not fix problem.
Thanks.

 

[tom]

restart also cman and pve-cluster filesystem

service cman restart

service pve-cluster restart

 

[TrollTech]

Thanks for help

To fix it:

service pvestatd restart

service cman restart

service pve-cluster restart

on all affected nodes.