Hello,
we have some problems with the vnc-console (especially via api) and pve 3.0/3.1.
I managed to open VNC-Sessions via. webinterface by increasing $timeout in /usr/share/perl5/PVE/API2/Qemu.pm to 20 (no other changes made so far).
VNC via. webinterface now works but needs one reload before opening the session.
Error from log:
pveversion:
VNC-Console via API however doesn't work at all (it times out with same error in log and offers to login again).
Other API-functions (like creating backups, changing vm settings, power-functions, ...) work perfectly.
We tried with different Java-versions and clients.
How can we get the vnc-console working on first-try (I think that would also the fix for the problem with api-vnc)?
we have some problems with the vnc-console (especially via api) and pve 3.0/3.1.
I managed to open VNC-Sessions via. webinterface by increasing $timeout in /usr/share/perl5/PVE/API2/Qemu.pm to 20 (no other changes made so far).
VNC via. webinterface now works but needs one reload before opening the session.
Error from log:
Code:
[COLOR=#000000][FONT=tahoma]no connection : Connection timed out[/FONT][/COLOR][COLOR=#000000][FONT=tahoma]
TASK ERROR: command '/bin/nc -l -p 5900 -w 20 -c '/usr/bin/ssh -T -o BatchMode=yes <ip4> /usr/sbin/qm vncproxy 695 2>/dev/null'' failed: exit code 1
[/FONT][/COLOR]
Code:
proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-22-pve)
pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-23-pve: 2.6.32-109
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.0-1
pve-cluster: 3.0-7
qemu-server: 3.1-1
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-10
pve-libspice-server1: 0.12.4-1
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2
Other API-functions (like creating backups, changing vm settings, power-functions, ...) work perfectly.
We tried with different Java-versions and clients.
How can we get the vnc-console working on first-try (I think that would also the fix for the problem with api-vnc)?