The VNC connection does not work WebUI

M

MrConstantine

New Member
Nov 22, 2017
5
0
1
31
Hello.
Please, help me.


pveversion -v

proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-35 (running version: 5.1-35/722cc488)
pve-kernel-4.13.4-1-pve: 4.13.4-25
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90

service pvedaemon status

Code: 
Nov 21 23:58:27 vps qm[25022]: VM 501 qmp command failed - VM 101 not running
Nov 21 23:58:27 vps pvedaemon[24539]: <account001@pve> end task UPID:vpspro-005:000061BC:073A9907:5A145B32:vncproxy:101:account001@pve: Failed to run vncproxy.

service pve-cluster status

Code: 
Nov 22 09:21:15 vps pmxcfs[32055]: [ipcs] crit: connection from bad user 65534! - rejected
Nov 22 09:21:15 vps pmxcfs[32055]: [libqb] error: Error in connection setup (32055-10061-14): Unknown error -1 (-1)
Nov 22 09:21:15 vps pmxcfs[32055]: [ipcs] crit: connection from bad user 65534! - rejected
Nov 22 09:21:15 vps pmxcfs[32055]: [libqb] error: Error in connection setup (32055-10061-14): Unknown error -1 (-1)
Nov 22 09:21:15 vps pmxcfs[32055]: [ipcs] crit: connection from bad user 65534! - rejected
Nov 22 09:21:15 vps pmxcfs[32055]: [libqb] error: Error in connection setup (32055-10061-14): Unknown error -1 (-1)
Nov 22 09:21:15 vps pmxcfs[32055]: [ipcs] crit: connection from bad user 65534! - rejected
Nov 22 09:21:15 vps pmxcfs[32055]: [libqb] error: Error in connection setup (32055-10061-14): Unknown error -1 (-1)
Nov 22 09:21:15 vps pmxcfs[32055]: [ipcs] crit: connection from bad user 65534! - rejected
Nov 22 09:21:15 vps pmxcfs[32055]: [libqb] error: Error in connection setup (32055-10061-14): Unknown error -1 (-1)


service pvestatd status

Code: 
Nov 22 14:45:21 vps pvestatd[1166]: ipcc_send_rec[1] failed: Transport endpoint is not connected
Nov 22 14:45:21 vps pvestatd[1166]: ipcc_send_rec[2] failed: Connection refused
Nov 22 14:45:21 vps pvestatd[1166]: ipcc_send_rec[3] failed: Connection refused
Nov 22 14:45:21 vps pvestatd[1166]: ipcc_send_rec[4] failed: Connection refused
Nov 22 14:45:21 vps pvestatd[1166]: status update error: Connection refused

Black screen through the VNC console and do nothing until you turn off the virtual machine. And then run it again and the console works. I can not cope with these mistakes.
 
MrConstantine said:
Black screen through the VNC console and do nothing until you turn off the virtual machine. And then run it again and the console works. I can not cope with these mistakes.
Click to expand...
i guess this is due to the guest turning off its displays, for windows you should disable the energy save modes

as for the following logs;
MrConstantine said:
Nov 22 14:45:21 vps pvestatd[1166]: ipcc_send_rec[1] failed: Transport endpoint is not connected
Nov 22 14:45:21 vps pvestatd[1166]: ipcc_send_rec[2] failed: Connection refused
Nov 22 14:45:21 vps pvestatd[1166]: ipcc_send_rec[3] failed: Connection refused
Nov 22 14:45:21 vps pvestatd[1166]: ipcc_send_rec[4] failed: Connection refused
Nov 22 14:45:21 vps pvestatd[1166]: status update error: Connection refused
Click to expand...

this has nothing to do with novnc, and point to a deeper problem with your setup,
you could post the status of your services:
Code: 
systemctl status pve-cluster pvestatd pveproxy pvedaemon
 
Hi.
On all Windows virtual machines, the power saving mode is turned off. And it does not help :( .

Code: 
root@vps:~# systemctl status pve-cluster pvestatd pveproxy pvedaemon
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
   Active: active (running) since Wed 2017-11-22 18:19:26 +07; 1 day 14h ago
  Process: 1280 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 1220 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=0/SUCCESS)
 Main PID: 1277 (pmxcfs)
   CGroup: /system.slice/pve-cluster.service
           └─1277 /usr/bin/pmxcfs

Nov 22 18:19:25 vps systemd[1]: Starting The Proxmox VE cluster filesystem...
Nov 22 18:19:26 vps systemd[1]: Started The Proxmox VE cluster filesystem.

● pvestatd.service - PVE Status Daemon
   Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled)
   Active: active (running) since Wed 2017-11-22 18:19:26 +07; 1 day 14h ago
  Process: 1330 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
 Main PID: 1346 (pvestatd)
   CGroup: /system.slice/pvestatd.service
           └─1346 pvestatd

Nov 23 00:01:20 vps pvestatd[1346]: status update time (10.837 seconds)
Nov 23 00:02:02 vps pvestatd[1346]: status update time (12.140 seconds)
Nov 23 00:39:37 vps pvestatd[1346]: status update time (14.219 seconds)
Nov 23 07:32:15 vps pvestatd[1346]: status update time (8.764 seconds)
Nov 23 08:05:40 vps pvestatd[1346]: got timeout
Nov 23 08:05:46 vps pvestatd[1346]: status update time (8.546 seconds)
Nov 23 08:41:13 vps pvestatd[1346]: status update time (15.989 seconds)
Nov 23 13:24:57 vps pvestatd[1346]: status update time (12.494 seconds)
Nov 24 06:54:29 vps pvestatd[1346]: status update time (8.544 seconds)
Nov 24 07:31:36 vps pvestatd[1346]: status update time (5.973 seconds)

● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
   Active: active (running) since Wed 2017-11-22 18:19:27 +07; 1 day 14h ago
  Process: 1355 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
 Main PID: 1362 (pveproxy)
   CGroup: /system.slice/pveproxy.service
           ├─1362 pveproxy
           ├─1845 pveproxy worker
           ├─1868 pveproxy worker
           └─1917 pveproxy worker

Nov 24 08:09:44 vps pveproxy[1916]: got inotify poll request in wrong process - disabling inotify
Nov 24 08:13:03 vps pveproxy[1916]: worker exit
Nov 24 08:25:03 vps pveproxy[1917]: problem with client 91.221.xx.xxx; rsa_padding_check_pkcs1_type_1: block type is not 01
Nov 24 08:25:03 vps pveproxy[1917]: Can't call method "timeout_reset" on an undefined value at /usr/share/perl5/PVE/HTTPServer.pm line 227.
Nov 24 08:25:04 vps pveproxy[1868]: problem with client 91.221.xx.xxx; rsa_padding_check_pkcs1_type_1: block type is not 01
Nov 24 08:25:04 vps pveproxy[1868]: Can't call method "timeout_reset" on an undefined value at /usr/share/perl5/PVE/HTTPServer.pm line 227.
Nov 24 08:25:04 vps pveproxy[1868]: problem with client 91.221.xx.xxx; rsa_padding_check_pkcs1_type_1: block type is not 01
Nov 24 08:25:04 vps pveproxy[1868]: Can't call method "timeout_reset" on an undefined value at /usr/share/perl5/PVE/HTTPServer.pm line 227.
Nov 24 08:25:05 vps pveproxy[1868]: problem with client 82.117.xx.xxx; rsa_eay_public_decrypt: padding check failed
Nov 24 08:25:05 vps pveproxy[1868]: Can't call method "timeout_reset" on an undefined value at /usr/share/perl5/PVE/HTTPServer.pm line 227.

● pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
   Active: active (running) since Wed 2017-11-22 18:19:27 +07; 1 day 14h ago
  Process: 1335 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
 Main PID: 1349 (pvedaemon)
   CGroup: /system.slice/pvedaemon.service
           ├─1349 pvedaemon
           ├─1350 pvedaemon worker
           ├─1351 pvedaemon worker
           └─1352 pvedaemon worker

Nov 24 08:22:10 vps pvedaemon[1352]: <root@pam> successful auth for user 'account001@pve'
Nov 24 08:25:34 vps pvedaemon[1352]: <root@pam> successful auth for user 'belozerov@pam'
Nov 24 08:25:55 vps pvedaemon[3540]: starting vnc proxy UPID:vps:00000DD4:00D15881:5A177523:vncproxy:601:belozerov@pam:
Nov 24 08:25:55 vps pvedaemon[1352]: <belozerov@pam> starting task UPID:vpspro-006:00000DD4:00D15881:5A177523:vncproxy:601:belozerov@pam:
Nov 24 08:26:02 vps pvedaemon[1351]: <belozerov@pam> starting task UPID:vpspro-006:00000DE6:00D15AF8:5A17752A:vncproxy:602:belozerov@pam:
Nov 24 08:26:02 vps pvedaemon[3558]: starting vnc proxy UPID:vps:00000DE6:00D15AF8:5A17752A:vncproxy:602:belozerov@pam:
Nov 24 08:26:06 vps pvedaemon[1351]: <belozerov@pam> starting task UPID:vps:00000DEA:00D15CDF:5A17752E:vncproxy:603:belozerov@pam:
Nov 24 08:26:06 vps pvedaemon[3562]: starting vnc proxy UPID:vps:00000DEA:00D15CDF:5A17752E:vncproxy:603:belozerov@pam:
Nov 24 08:26:11 vps pvedaemon[1351]: <belozerov@pam> starting task UPID:vps:00000DFB:00D15EB1:5A177533:vncproxy:604:belozerov_ke@pam:
Nov 24 08:26:11 vps pvedaemon[3579]: starting vnc proxy UPID:vps:00000DFB:00D15EB1:5A177533:vncproxy:604:belozerov@pam:

For some reason, the Internet connection with virtual machines is lost.

Can I try to increase the timeout to 60?

/usr/share/perl5/PVE/HTTPServer.pm

Code: 
my $w; $w = http_request(
            $method => $target,
            headers => $headers,
            timeout => 30,
            recurse => 0,
            proxy => undef, # avoid use of $ENV{HTTP_PROXY}
            keepalive => $keep_alive,
            body => $content,
            tls_ctx => AnyEvent::TLS->new(%{$tls}),


Thank you!
 
Last edited:
MrConstantine said:
Nov 23 00:01:20 vps pvestatd[1346]: status update time (10.837 seconds) Nov 23 00:02:02 vps pvestatd[1346]: status update time (12.140 seconds) Nov 23 00:39:37 vps pvestatd[1346]: status update time (14.219 seconds) Nov 23 07:32:15 vps pvestatd[1346]: status update time (8.764 seconds) Nov 23 08:05:40 vps pvestatd[1346]: got timeout
Click to expand...
those probably are because of a slow storage somewhere (those updates should not take so much time)

MrConstantine said:
Nov 24 08:25:03 vps pveproxy[1917]: problem with client 91.221.xx.xxx; rsa_padding_check_pkcs1_type_1: block type is not 01
Click to expand...
look here:
https://forum.proxmox.com/threads/n...heck_pkcs1_type_1-block-type-is-not-01.16848/

MrConstantine said:
For some reason, the Internet connection with virtual machines is lost.

Can I try to increase the timeout to 60?

/usr/share/perl5/PVE/HTTPServer.pm
Click to expand...
what do you mean exactly, those setting there has nothing to do with vm internet connection
 
And how then to explain that virtual servers with the operating system Windows 8.1 work and after a while the connection with the VNC (HTML5) WebGUI is lost.
Do not respond to keystrokes and black screen.
It's strange. There is no hibernation mode.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back