failed reading ticket: connection closed before authentication

[James Crook]

So we keep getting this error on a lot of workstations when we have been logged into the host (with firefox, chrome or IE)
it seems to happen randomly, but when we come back to the logged in session and click on a console for a container we get get "failed"

if you look into the logs it says

client connection: V4(127.0.0.1:44720)
failed reading ticket: connection closed before authentication
TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/18002 --perm VM.Console -- /usr/bin/ssh -e none -t 10.0.0.48 -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole18002 -r winch -z lxc-console -n 18002 -e -1' failed: exit code 1

If we close and reopen the whole browser or reboot the issues goes away for a while.

 

[oguz]

hi,

what is your pveversion -v?

does the issue happen on containers only? or also with VMs?

can you post some of the configuration files for the guests? (qm config VMID for VM and pct config CTID for containers, replace VMID/CTID with guest number)

 

[James Crook]

We only have containers, i'm unsure if it happens when trying to connect to the host as well tho, will see when it next happens

IP and MAC have been changed to protect the innocent

arch: amd64
cmode: console
cores: 2
hostname: SV1000-Test-SUSE15.2
memory: 2048
nameserver: 8.8.8.8 8.8.4.4 1.1.1.1
net0: name=eth0,bridge=vmbr6,firewall=1,gw=1.1.1.2,hwaddr=11:11:11:11:11:11,ip=1.1.1.1/24,type=veth
ostype: opensuse
rootfs: tank:subvol-18013-disk-0,size=100G
searchdomain: Test-SUSE.local
swap: 2048

Proxmox
Virtual Environment 6.4-13
Node 'ProxMoxNode1'
CPU usage
 
36.58% of 12 CPU(s)
    
IO delay
 
0.00%
Load average
 
12.54,12.14,11.32
RAM usage
 
77.47% (42.47 GiB of 54.82 GiB)
    
KSM sharing
 
0 B
HD space(root)
 
20.47% (19.24 GiB of 93.99 GiB)
    
SWAP usage
 
0.13% (10.83 MiB of 8.00 GiB)
CPU(s)
 
12 x Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz (1 Socket)
Kernel Version
 
Linux 5.4.140-1-pve #1 SMP PVE 5.4.140-1 (Wed, 08 Sep 2021 16:21:59 +0200)
PVE Manager Version
 
pve-manager/6.4-13/9f411e79
Logs
()
proxmox-ve: 6.4-1 (running kernel: 5.4.140-1-pve)
pve-manager: 6.4-13 (running version: 6.4-13/9f411e79)
pve-kernel-5.4: 6.4-6
pve-kernel-helper: 6.4-6
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.140-1-pve: 5.4.140-1
pve-kernel-5.4.128-1-pve: 5.4.128-2
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.73-1-pve: 5.4.73-1
pve-kernel-5.4.65-1-pve: 5.4.65-1
pve-kernel-5.4.55-1-pve: 5.4.55-1
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.4.41-1-pve: 5.4.41-1
pve-kernel-4.15: 5.4-12
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.13-1-pve: 5.3.13-1
pve-kernel-4.15.18-24-pve: 4.15.18-52
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.17-1-pve: 4.15.17-9
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.13-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-1
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.3-1
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.5-pve1~bpo10+1

 

[oguz]

is this a cluster?

we recently released PVE 7.1 so it might be worth a try to upgrade your servers and see if the issues still happen

[0]: https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0

 

[James Crook]

It is a cluster (sorry should have said that)

can't upgrade to 7.1 as we have containers that have an old version of systemd

 

[sipelaut]

i have problem to
like this

client connection: 127.0.0.1:42874
failed reading ticket: connection closed before authentication
TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/105 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole105 -r winch -z lxc-console -n 105 -e -1' failed: exit code 1

can anyone explain this error ?

 

[Michael.Uray]

Similar problem here after login and reloading website or going to start the backup.

"Some errors have been encountered: xxx"
"Connection error 401: No ticket"

I am using WebAuthn if that is relevant.
This happens on two machines with no-subscription.

I have two other machines with subcription and no WebAuthn, there it seems it does not happen.