VNC stopped working

makno

Renowned Member
Mar 29, 2010
9
0
66
Good afternoon,

i had a look around but couldn't find any other posts with same issue so here is the problem:

randomly one day the vnc console stopped working, this mean i cannot open vnc through the web interface on any VM.

I have tried restarting the cluster and updating to the latest release but the problem persists. It just looks like vnc is not triggered from the webpanel.

Any ideas?

Let me know if you need any prints
 
looks like java applet issue on your desktop. what OS do you use?
 
thanks for the reply but sorry that's not the case, tried with thew following:

XP- firefox, chrome, IE
WIN7 - firefox, chrome, IE
Ubuntu: firefox

it looks like the trigger from the webinterface doesn't do anything, the pop-up it's completely blank however if i use the command line from the cluster and than connect with ultravnc i can get in. As i said it just stopped working one day
 
if you can connect via ultravnc it seems you did some tweaking.?
vnc console should work well on these desktop systems with java installed (check via http://java.com)

and post the output of 'pveversion -v'
 
hi tom,

thanks again for the reply, i can connect with vnc by loggin on the cluster in ssh and issuing:

nc -l -p 5900 -c "qm vncproxy 108 password"

after that i connect using UltraVNC to the cluster ip and using the selected password.

The output of 'pveversion -v is:
pve-manager: 1.7-10 (pve-manager/1.7/5323)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.32: 1.7-30
pve-kernel-2.6.32-4-pve: 2.6.32-30
pve-kernel-2.6.24-10-pve: 2.6.24-21
qemu-server: 1.1-28
pve-firmware: 1.0-10
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-10
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1dso1
pve-qemu-kvm: 0.13.0-3
ksm-control-daemon: 1.0-4
 
you pveversion -v shows that you got some wrong packages installed. you installed the virtual package for 2.6.32 (proxmox-ve-2.6.32) but you still boot 2.6.24 kernel.

pls follow this guide to fix:
http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_to_1.7

and take a look on the boot order in /boot/grub/menu.lst, make sure you boot the 2.6.32er kernel.

after you got it fixed you should get the following:

Code:
pveversion -v
pve-manager: 1.7-11 (pve-manager/1.7/5470)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.7-30
pve-kernel-2.6.32-4-pve: 2.6.32-30
qemu-server: 1.1-28
pve-firmware: 1.0-10
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-10
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.13.0-3
ksm-control-daemon: 1.0-4
I am not sure if it fixes your issue but you need to correct this in any case.