TASK ERROR: Failed to run vncproxy.

[yunmkfed]

Hi,

As from today one VM (Windows Server 2016) has generated this error twice.

VM 100 qmp command 'set_password' failed - got timeout
TASK ERROR: Failed to run vncproxy.

I log into it using RD and as soon as I open Firefox it tells me that Firefox is updating at which point:
* The RD connection drops
* Proxmox spikes for this VM (CPU, Memory, Network)

After a few minutes, the VM settles down and I can access it again. Firefox is at 126.0.1

 

[fiona]

Hi,
please share the output of pveversion -v and qm config 100, as well as the system log/journal from around the time the issue happened. How did the load on the host look like around the time the issue happened?

 

[yunmkfed]

Hello,

I attached all the output. It happened twice around the 7:30 and 10:30 time. While I don't log into the VM every day it it normally is reactive when I log into it. My impression is that Firefox browser was updating when this manifested itself (twice). I logged in just now and everything seems to be operating well.

The only think I can think of is that I have a backup that backup up the VMs every 1st of the month. The backup did not report any issues.

Thanks



Output of pveversion -v:

Linux pve1 6.8.4-3-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.4-3 (2024-05-02T11:55Z) x86_64


The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.


Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Jun  3 07:39:44 CEST 2024 on pts/0
root@pve1:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.4-3-pve)
pve-manager: 8.2.2 (running version: 8.2.2/9355359cd7afbae4)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.4-3
proxmox-kernel-6.8.4-3-pve-signed: 6.8.4-3
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
proxmox-kernel-6.5.13-5-pve-signed: 6.5.13-5
proxmox-kernel-6.5: 6.5.13-5
proxmox-kernel-6.5.13-3-pve-signed: 6.5.13-3
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
ceph-fuse: 17.2.7-pve2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.6
libpve-cluster-perl: 8.0.6
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.1
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.2.1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.2-1
proxmox-backup-file-restore: 3.2.2-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.6
pve-container: 5.1.10
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.0
pve-firewall: 5.0.7
pve-firmware: 3.11-1
pve-ha-manager: 4.0.4
pve-i18n: 3.2.2
pve-qemu-kvm: 8.1.5-6
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.3-pve2

Output of qm config 100:

agent: 1
balloon: 8192
boot: order=sata0;ide2;net0
cores: 4
cpu: x86-64-v2-AES
ide2: none,media=cdrom
machine: pc-q35-8.1
memory: 12288
meta: creation-qemu=8.1.5,ctime=1708943101
name: vm-onn
net0: e1000=BC:24:11:B2:71:1C,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win11
sata0: hdd-dir:100/vm-100-disk-1.qcow2,size=128G
sata1: hdd-dir:100/vm-100-disk-0.qcow2,size=32G
scsihw: virtio-scsi-single
smbios1: uuid=18f71c74-a405-461d-b7ea-01c780f4a7e2
sockets: 4
startup: order=2
usb0: spice
vmgenid: 64afd86a-0cee-44d7-8193-70ebd6500a4a

 

[fiona]

Unfortunately nothing obvious pointing to the cause of the issue in the logs. How did the load on the host look like around the time the issue happened? E.g. you can check the usage graph's in the node's Summary in the UI.

 

[yunmkfed]

There seems to be a spike in CPU and network traffic.

I was connected using RD and opened a process that, in turn invoked Firefox. Firefox was updating itself at the point the RD session abruptly terminated and this situation manifested itself.

Once the machine recovered I tried again for a second time with the same outcome.

It did not happen afterwards.