Unable to get data for Cluster Node 0 debian 5 proxmox ve 1.8

  • Thread starter Thread starter spacemind
  • Start date Start date
S

spacemind

Guest
Hi,

I have installed proxmox ve 1.8 on a Default debian installation.

All runned ok for a few days with 4 KVM´s, today i am getting this error in the VirtualMachines menu:

"Unable to get data for Cluster Node 0"
"Unable to load local cluster table"

If i click several times in the Virtual Machines menu link, i can see the VM`s flashing and disapearing.

I did not update/upgrade my debian since the instalation.

Informations:

Kernel:
Linux debian.proxmox 2.6.32-4-pve #1 SMP Mon May 9 12:59:57 CEST 2011 x86_64 GNU/Linux
Linux version 2.6.32-4-pve (unknown) (root@oahu) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Mon May 9 12:59:57 CEST 2011

Proxmox version:

debian:/home/MTR# pveversion -v
pve-manager: 1.8-17 (pve-manager/1.8/5948)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.8-33
pve-kernel-2.6.32-4-pve: 2.6.32-33
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.26-1pve4
vzdump: 1.2-12
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.0-3
ksm-control-daemon: 1.0-5
debian:/home/MTR#



I am able to access the PVE from web/ssh, but the VM´s are hanged, no access. I do not want to reboot because i need to find the problem.


Any help ?

Thanks
 
never seen. could be a network issue, check this.

any hint in the syslog/dmesg?
 
Hi,

I have figured out the problem, but i cannot solve it.

I have found that the /var space is 20gb and its 100% used.

I have moved the ISO, and the vmware viles (.raw) files to /home/vz/x.... and created a symbolic link inside the vz folder in /var.


I can see now the vm machines but i cannot start them.

pvedaemon 6225 VM 103 start failed - Connection refused


[TABLE="class: menubg lightcolbd, width: 747"]
[TR]
[TD="align: right"]Service: anyCronNTPKernelPVE daemonPVE cluster syncPVE cluster vpnApache[/TD]
[/TR]
[/TABLE]
Jun 17 19:00:03 pvedaemonVM 103 start failed - Connection refused
Jun 17 19:05:40 pvedaemonVM 102 start failed - Transport endpoint is not connected

[TD="align: right"]6225 [/TD]

[TD="align: right"]6542 [/TD]



Any help ?
 
Last edited by a moderator:
this means your root partition is full which will cause multiple issues, remove some files. the root partition should not be used to store data.

a default installation will got most space in the data volume group, mounted on /var/lib/vz

see 'df -h'