The nodes display does not normally，but works 2015

[tinolin]

Good morning ! the same thing happens in this post : http://forum.proxmox.com/threads/12316-The-nodes-display-does-not-normally，but-works


but, my version of Proxmox pve is:


root@proxmox:~# pveversion -v
proxmox-ve-2.6.32: 3.2-126 (running kernel: 2.6.32-29-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-29-pve: 2.6.32-126
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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1


as I solve this without updating ?

from already thank you very much !

 

[tinolin]

someone?

 

[tinolin]

[SOLVED ]Re: The nodes display does not normally，but works 2015

Solved:pvestatd restart
pvecm updatecerts
pveproxy restart

 

[tinolin]

Re: [SOLVED ]Re: The nodes display does not normally，but works 2015

Some details:

He turned to break the interface, after a few minutes, you run the above command "pvestatd restart"; then, wanting to restart the service pvestad, threw the following message: "ERROR: cannot acquire lock '/var/run/pvestatd.pid.lock' - Resource temporarily unavailable".


Googling I discovered that it is a bug with the resources NFS mounted. Therefore disassemble with "umount /my-nfs-resource " and the command pvestats then restart correctly.


Those are all I wanted to add.


Greetings.