VNC console error after last kernel upadte

alain

Renowned Member
May 17, 2009
224
2
83
France/Paris
Hi all,

I just did an update of my test PVE 2.0 install (upgraded from RC1), that provides last kernel. I then did a test for USB passthrough, that was successfull (reported elsewhere).

But I encounter a very annoying problem. VNC console does not seem to work now. I have this error message :
<code>
no connection : Connection timed out
TASK ERROR: command '/bin/nc -l -p 5900 -w 10 -c '/usr/sbin/qm vncproxy 101 2>/dev/null'' failed: exit code 1
</code>

Does anyone sees this problem ? I did nothing special, apart mounting this USB stick, so I wonder what happens there...

root@lx-ape3:/etc/qemu-server# pveversion -v
pve-manager: 2.0-57 (pve-manager/2.0/ff6cd700)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-65
pve-kernel-2.6.32-11-pve: 2.6.32-65
pve-kernel-2.6.32-6-pve: 2.6.32-55
lvm2: 2.02.88-2pve2
clvm: 2.02.88-2pve2
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-36
pve-firmware: 1.0-15
libpve-common-perl: 1.0-25
libpve-access-control: 1.0-17
libpve-storage-perl: 2.0-17
vncterm: 1.0-2
vzctl: 3.0.30-2pve2
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

Alain
 
It was a Java problem. I was using Firefox 11.0, I tried with Chrome and got message saying I had to update Java plugin to last version, .31. I did, and afterwhile, VNC console opened smoothly.

I did the same thing for Firefox (update Java plugin to the same version), and again it is working.

Sorry for the noise.

Alain
 
Last edited: