Open Spice on two of three hosts fails after update

[fireon]

Hello all,

after some update i'am not able to open a spicewindows on 2 from 3 hosts. Here are the error message:

Okt 27 01:27:44 backup pvedaemon[32617]: launch command: /usr/bin/spiceterm --port 61000 --addr 127.0.0.1 --timeout 40 --authpath /vms/111 --permissions VM.Console --keymap de -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole111 -r winch -z lxc-console -n 111
Okt 27 01:27:44 backup pvedaemon[32617]: spiceterm failed\n: got signal 5
Okt 27 01:27:44 backup kernel: traps: spiceterm[32618] trap int3 ip:7f7f6e14e261 sp:7ffe49a695b0 error:0 in libglib-2.0.so.0.5000.3[7f7f6e0fe000+112000]

Problem exists about a week.

Here are my pveversion:

proxmox-ve: 5.2-2 (running kernel: 4.15.18-7-pve)
pve-manager: 5.2-10 (running version: 5.2-10/6f892b40)
pve-kernel-4.15: 5.2-10
pve-kernel-4.15.18-7-pve: 4.15.18-27
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.18-3-pve: 4.15.18-22
pve-kernel-4.15.18-2-pve: 4.15.18-21
pve-kernel-4.15.18-1-pve: 4.15.18-19
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-40
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-30
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-3
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-28
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
pve-zsync: 1.7-1
qemu-server: 5.0-36
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.11-pve1~bpo1

Thanks a lot and best regards.

 

[dcsapak]

Okt 27 01:27:44 backup pvedaemon[32617]: spiceterm failed\n: got signal 5

anything on your system that would send a SIGTRAP ?

 

[fireon]

Not that I know of. There are normal with ISO/USB Proxmoxinstallation. Since an update spice is only on 2 of three hosts not working anymore. Tested in various browsers. Srange thing in webconsole @task there is an OK flag, but i got also the message "Timeout while waiting for port '61000' to get ready! (500)" after clicking on Spice.

 

[fireon]

anything on your system that would send a SIGTRAP ?

Another idea? Why it opens only on one host...?

 

[dcsapak]

is it only with spiceterm, or does it also happen when you connect to a vm with spice?

 

[fireon]

Only with Spiceterm from an Client. If i connect to a Spicevm with novnc it is working fine. I've also tested it directly without webbrowser with the script under documentations.

 

[fireon]

New tests. Only LXC's didn't work on the other Hosts. I created an KVM with Spice on one node an this is working fine. Also migrate a existing KVM/Spice machine to an other node, and this is also working fine, only LXC's didn't work and only on this two nodes from three.

 

[dcsapak]

only on this two nodes from three.

are those hosts by any chance in a cluster, and are you connecting always to the same host, and does it work with the containers that are on that host?

 

[fireon]

Yes they are in a cluster. If i connect to the first host that is working fine i can call all vm's and containers normaly, also with spice (virt-viewer). If i do this with other containers on the other two nodes, i got these errors.

I've tested this by migration with working containers from the first host to the others, same error. I also created a new container on these other two hosts, same error. If i migrate one of this new containers to the first host/node, it's working fine with spice (virt-viewer). I also tested to login from another node with pve webinterface. Same Errors.

 

[dcsapak]

I also tested to login from another node with pve webinterface. Same Errors.

same errors on the same hosts? or does only 'local' spice work ?

 

[fireon]

same errors on the same hosts? or does only 'local' spice work ?

No, same Error on the same hosts. So i mean if i connect to another node the local spice didn't work, but the spice from the remote hosts, what i meant with first host/node. So yes, absoulty same errors.

 

[dcsapak]

No, same Error on the same hosts. So i mean if i connect to another node the local spice didn't work, but the spice from the remote hosts, what i meant with first host/node. So yes, absoulty same errors.

ok thank you for your patience, i still cannot reproduce it here, but i will try some things