Proxmox Server Webgui Shell no shell prompt

A

adoII

Renowned Member
Jan 28, 2010
182
19
83
Since a few weeks i do not get a working shell when i click on a proxmox-server and then on "_ Shell" in the proxmox webgui.

The process is hanging with a blinking cursor but the prompt does not show up.

Sometimes I get a prompt when i try multiple times to open the root shell.

This happens on multiple Servers and also directly after reboot. All these Servers have 8.4.1 Environment with all new patches Installed. This also happens directly after a new install of a proxmox Server.

Is this a known issue ? Is there a workaround ?
 
when typing it is like i am typing white characters on a black canvas. The system does not react on whatever I type. Also ctrl+c echos a ^c on the canvas. When i go to another menu and then go back to shell sometimes it will work after a few tries.
 
adoII said:
when typing it is like i am typing white characters on a black canvas. The system does not react on whatever I type. Also ctrl+c echos a ^c on the canvas. When i go to another menu and then go back to shell sometimes it will work after a few tries.
Click to expand...
Could you give more information on your setup please and outline steps to reproduce (i.e. what you did to end up in this state)?
 
This is a blank installed AX42 Server from Hetzner installed on monday. I always install a blank debian 12 linux with hetzner installimage and then follow the procedure to install proxmox ve on a debian bookworm here .
I have the same problem with some other AX52 servers from hetzner installed last year.

I install current proxmox bookworm pve-no-subscription upodates every day so all servers have current patchlevels.

Here are the versions:
Code: 
proxmox-ve: 8.4.0 (running kernel: 6.8.12-10-pve)
pve-manager: 8.4.1 (running version: 8.4.1/2a5fa54a8503f96d)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.8.12-10-pve-signed: 6.8.12-10
proxmox-kernel-6.8: 6.8.12-10
amd64-microcode: 3.20240820.1~deb12u1
ceph-fuse: 16.2.15+ds-0+deb12u1
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
dnsmasq: 2.90-4~deb12u1
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx11
intel-microcode: 3.20250211.1~deb12u1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.0
libpve-cluster-perl: 8.1.0
libpve-common-perl: 8.3.1
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.6
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.6.0-2
proxmox-backup-client: 3.4.1-1
proxmox-backup-file-restore: 3.4.1-1
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.2
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.3.10
pve-cluster: 8.1.0
pve-container: 5.2.6
pve-docs: 8.4.0
pve-edk2-firmware: not correctly installed
pve-firewall: 5.1.1
pve-firmware: 3.15-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.2
pve-qemu-kvm: 9.2.0-5
pve-xtermjs: 5.5.0-2
qemu-server: 8.3.12
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
 
adoII said:
This is a blank installed AX42 Server from Hetzner installed on monday. I always install a blank debian 12 linux with hetzner installimage and then follow the procedure to install proxmox ve on a debian bookworm here .
I have the same problem with some other AX52 servers from hetzner installed last year.

I install current proxmox bookworm pve-no-subscription upodates every day so all servers have current patchlevels.

Here are the versions:
Code: 
proxmox-ve: 8.4.0 (running kernel: 6.8.12-10-pve)
pve-manager: 8.4.1 (running version: 8.4.1/2a5fa54a8503f96d)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.8.12-10-pve-signed: 6.8.12-10
proxmox-kernel-6.8: 6.8.12-10
amd64-microcode: 3.20240820.1~deb12u1
ceph-fuse: 16.2.15+ds-0+deb12u1
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
dnsmasq: 2.90-4~deb12u1
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx11
intel-microcode: 3.20250211.1~deb12u1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.0
libpve-cluster-perl: 8.1.0
libpve-common-perl: 8.3.1
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.6
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.6.0-2
proxmox-backup-client: 3.4.1-1
proxmox-backup-file-restore: 3.4.1-1
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.2
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.3.10
pve-cluster: 8.1.0
pve-container: 5.2.6
pve-docs: 8.4.0
pve-edk2-firmware: not correctly installed
pve-firewall: 5.1.1
pve-firmware: 3.15-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.2
pve-qemu-kvm: 9.2.0-5
pve-xtermjs: 5.5.0-2
qemu-server: 8.3.12
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
Click to expand...
And what steps were you trying to take? What sort of VM was it?
 
it is not the vm that shows no cursor, it is the proxmox server "Shell" itself. the vms are debian and there is no problem with vm consoles.
 
adoII said:
it is not the vm that shows no cursor, it is the proxmox server "Shell" itself. the vms are debian and there is no problem with vm consoles.
Click to expand...
Are you referring to the shell of your "root node"?
 
adoII said:
it is not the vm that shows no cursor, it is the proxmox server "Shell" itself. the vms are debian and there is no problem with vm consoles.
Click to expand...
Just to rule out excessive RAM usage: Could you perhaps show a screenshot of your root node's RAM usage? Is it possible for you to SSH into your root node? What does journalctl show you?
 
There is plenty of RAM, only 6 GB of 64 GB in use.
The journalctl does not give any hint see below.

SSH and everything else using the proxmox web-interface is working perfectly-

I have another idea, maybe it has to do something with hetzner and mtu packet sizes (but why only with vnc). I will dive into that theory ...

Code: 
ay 15 10:14:30 pmx01 pvedaemon[271961]: starting termproxy UPID:pmx01:00042659:007843BF:6825A266:vncshell::root@pam:
May 15 10:14:30 pmx01 pvedaemon[249139]: <root@pam> starting task UPID:pmx01:00042659:007843BF:6825A266:vncshell::root@pam:
May 15 10:14:30 pmx01 pvedaemon[251824]: <root@pam> successful auth for user 'root@pam'
May 15 10:14:30 pmx01 login[271964]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
May 15 10:14:30 pmx01 systemd-logind[611]: New session 62 of user root.
May 15 10:14:30 pmx01 systemd[1]: Started session-62.scope - Session 62 of User root.
May 15 10:14:30 pmx01 login[271969]: ROOT LOGIN  on '/dev/pts/1'
 
Meanwhile I found out that mtu has nothing to do with it. But I found that the problem only occurs in Firefox, even in private window or after clearing cache. Using chromium I never have the problem.
 
  • Like
Reactions: Kingneutron
adoII said:
There is plenty of RAM, only 6 GB of 64 GB in use.
The journalctl does not give any hint see below.

SSH and everything else using the proxmox web-interface is working perfectly-

I have another idea, maybe it has to do something with hetzner and mtu packet sizes (but why only with vnc). I will dive into that theory ...

Code: 
ay 15 10:14:30 pmx01 pvedaemon[271961]: starting termproxy UPID:pmx01:00042659:007843BF:6825A266:vncshell::root@pam:
May 15 10:14:30 pmx01 pvedaemon[249139]: <root@pam> starting task UPID:pmx01:00042659:007843BF:6825A266:vncshell::root@pam:
May 15 10:14:30 pmx01 pvedaemon[251824]: <root@pam> successful auth for user 'root@pam'
May 15 10:14:30 pmx01 login[271964]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
May 15 10:14:30 pmx01 systemd-logind[611]: New session 62 of user root.
May 15 10:14:30 pmx01 systemd[1]: Started session-62.scope - Session 62 of User root.
May 15 10:14:30 pmx01 login[271969]: ROOT LOGIN  on '/dev/pts/1'
Click to expand...
Is that the complete output you have? Are there any messages when you try to access the web interface?
 
yes , this is the complete log i have. In the console I see the login is successfull but there never appears a shell prompt. This only happens with my firefox. I found out with chrome it is working.
 
adoII said:
yes , this is the complete log i have. In the console I see the login is successfull but there never appears a shell prompt. This only happens with my firefox. I found out with chrome it is working.
Click to expand...
Could you send a screenshot?
 
I am not able to send a screenshot. Today like magic the problem disappeared on all proxmox servers i have access to. It seems it was a Browser problem, something with cache or temporary data. I think I cleared all data in my Browser yesterday.
 
  • Like
Reactions: aabraham
adoII said:
I am not able to send a screenshot. Today like magic the problem disappeared on all proxmox servers i have access to. It seems it was a Browser problem, something with cache or temporary data. I think I cleared all data in my Browser yesterday.
Click to expand...
That can cause problems sometimes. :) I'm glad you were able to resolve it.
 
You must log in or register to reply here.
Top Bottom