Web interface partially works

P

Pilat

New Member
Aug 21, 2010
29
0
1
Hello!

proxmox2_1.png

All VM marked as stopped in the left list, but if you select a virtual machine in the summary shows that it is running. Backup ended successfully a few hours ago. Virtual machines are working .

What can be done to restore functionality of the web interface?


root@proxmox2:/var/log# pveversion -v
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-11-pve: 2.6.32-66
pve-kernel-2.6.32-16-pve: 2.6.32-80
pve-kernel-2.6.32-12-pve: 2.6.32-68
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
Click to expand...
 
looks like your cluster communication is down, or a storage is offline.

check syslog and you storage definitions. and try restarting pve-cluster (service pve-cluster restart)
 
tom said:
looks like your cluster communication is down, or a storage is offline.

check syslog and you storage definitions. and try restarting pve-cluster (service pve-cluster restart)
Click to expand...

cluster works - migration from web interface (offline) sussesful, in /var/log/messages once these messages look as incorrect:

Nov 6 02:03:14 proxmox2 kernel: EXT3-fs: barriers disabled
Nov 6 02:03:14 proxmox2 kernel: kjournald starting. Commit interval 5 seconds
Nov 6 02:03:14 proxmox2 kernel: EXT3-fs (dm-2): using internal journal
Nov 6 02:03:15 proxmox2 kernel: EXT3-fs (dm-2): 16 orphan inodes deleted
Nov 6 02:03:15 proxmox2 kernel: EXT3-fs (dm-2): recovery complete
Nov 6 02:03:15 proxmox2 kernel: EXT3-fs (dm-2): mounted filesystem with ordered data mode
Nov 6 02:35:50 proxmox2 kernel: EXT3-fs: barriers disabled
Nov 6 02:35:50 proxmox2 kernel: kjournald starting. Commit interval 5 seconds
Nov 6 02:35:50 proxmox2 kernel: EXT3-fs (dm-2): using internal journal
Nov 6 02:35:50 proxmox2 kernel: EXT3-fs (dm-2): 16 orphan inodes deleted
Nov 6 02:35:50 proxmox2 kernel: EXT3-fs (dm-2): recovery complete
Nov 6 02:35:50 proxmox2 kernel: EXT3-fs (dm-2): mounted filesystem with ordered data mode
Nov 6 02:36:19 proxmox2 kernel: EXT3-fs: barriers disabled
Nov 6 02:36:19 proxmox2 kernel: kjournald starting. Commit interval 5 seconds
Nov 6 02:36:19 proxmox2 kernel: EXT3-fs (dm-2): using internal journal
Nov 6 02:36:19 proxmox2 kernel: EXT3-fs (dm-2): 16 orphan inodes deleted
Nov 6 02:36:19 proxmox2 kernel: EXT3-fs (dm-2): recovery complete
Nov 6 02:36:19 proxmox2 kernel: EXT3-fs (dm-2): mounted filesystem with ordered data mode
Nov 6 02:38:25 proxmox2 kernel: EXT3-fs: barriers disabled
Click to expand...

service pve-cluster restart without effect...
 
dietmar said:
I guess this is the pvestatd bug we already fixed. Please can you update your installation?
Click to expand...

He's alive! Thanks!!!

root@proxmox2:~# aptitude upgrade
The following packages will be upgraded:
libpve-common-perl pve-manager qemu-server

...

Setting up libpve-common-perl (1.0-37) ...
Setting up pve-manager (2.2-26) ...
Restarting PVE Daemon: pvedaemon.
Restarting PVE Status Daemon: pvestatdstart-stop-daemon: warning: failed to kill 3122: No such process
.
Restarting web server: apache2 ... waiting .

Current status: 0 updates [-3].
root@proxmox2:~#
Click to expand...
 
Hello,

I had exactly the same issue with pvestatd not started. After "# service pvestatd start" all went OK.

Thank you.
 
You must log in or register to reply here.
Top Bottom
Back