[SOLVED] Console seems to have broken on 5.2-7

[Elfy]

Hi all,

The title says it all. When attempting to connect to the console via web-interface, I get a blank screen with a cursor. I'm currently using Firefox. The console worked just fine in 5.2-6. Connecting to the node via ">_Shell" works just fine.

Spoiler: Screenshot #1

Spoiler: Screenshot #2

Syslog around the time I tried to connect:

Aug 20 13:29:19 Wash pmxcfs[1767]: [status] notice: received log
Aug 20 13:29:21 Wash pmxcfs[1767]: [status] notice: received log
Aug 20 13:29:21 Wash sshd[12677]: Accepted publickey for root from 192.168.0.2 port 42910 ssh2: RSA SHA256:dARezFkLlMtEphuYXUroMJcaK6TP4DDKU8hS4fnf8ks
Aug 20 13:29:21 Wash sshd[12677]: pam_unix(sshd:session): session opened for user root by (uid=0)
Aug 20 13:29:21 Wash systemd-logind[907]: New session 36 of user root.
Aug 20 13:29:21 Wash systemd[1]: Started Session 36 of user root.
Aug 20 13:29:26 Wash sshd[12677]: Received disconnect from 192.168.0.2 port 42910:11: disconnected by user
Aug 20 13:29:26 Wash sshd[12677]: Disconnected from 192.168.0.2 port 42910
Aug 20 13:29:26 Wash sshd[12677]: pam_unix(sshd:session): session closed for user root
Aug 20 13:29:26 Wash systemd-logind[907]: Removed session 36.
Aug 20 13:29:26 Wash pmxcfs[1767]: [status] notice: received log

Steps I have tried:

• Clear browser history/cache
• Tried IE and Chrome
• Attempted to SSH from node console to add SSH key

 

[schinzelh]

Yep, same here: console on 5.2-6 worked fine, after updating to 5.2-7 it stopped working.

 

[Tuckie]

Same problem for me.

Edit: As a workaround, connecting via lxc-attach is still working. e.g. lxc-attach 102 from the host shell.

 

[dcsapak]

@Elfy

your screenshot1 shows the host console

your screenshot2 shows a container console, where it can be necessary to press 'enter' or another key once to actually get output (because the container already sent a console output which nobody captured)

 

[schinzelh]

@Elfy

your screenshot1 shows the host console

your screenshot2 shows a container console

Which is what he wrote: Host console (">_Shell") works fine, container console does not.

Pressing Enter in the container console does not solve it. Like i wrote: This worked in 5.2-6 and stopped working in 5.2-7.

 

[dcsapak]

can you post the container config?

 

[schinzelh]

can you post the container config?

Not sure how this could help - i am running 200+ containers on this cluster. All their consoles stopped working after updating to pve-manager 5.2-7.

Here you go:

cat /etc/pve/nodes/pmx02/lxc/10271.conf
arch: amd64
cores: 2
hostname: dd-apollo13
memory: 4096
nameserver: 8.8.8.8 9.9.9.9
net0: name=eth0,bridge=vmbr000,gw=XXXXXXXX,hwaddr=9A:80:43:F4:70:F8,ip=XXXXXXX/32,type=veth
ostype: ubuntu
rootfs: ceph-lxc:vm-10271-disk-1,size=40G
searchdomain: schinzel.org
swap: 256

 

[dcsapak]

this is a bug https://bugzilla.proxmox.com/show_bug.cgi?id=1854 the fix should be already on pvetest (package is lxc-pve)

 

[schinzelh]

this is a bug https://bugzilla.proxmox.com/show_bug.cgi?id=1854 the fix should be already on pvetest (package is lxc-pve)

Thanks - i have installed lxc-pve 3.0.2+pve1-1 from pvetest now, but it still does not work.

 

[dcsapak]

did you shutdown and start the container after installing the package?

 

[schinzelh]

did you shutdown and start the container after installing the package?

That did the trick, thanks!

So solution for now is

1. add

   deb http://download.proxmox.com/debian/pve stretch pvetest

   to your

   /etc/apt/sources.list

2. apt-get update ; apt-get install lxc-pve=3.0.2+pve1-1

3. shutdown and restart all containers
4. remove pvetest from sources.list again

Thanks again

 

[Elfy]

Hi all,

@dcsapak and @schinzelh Thank you for the suggestion and write-up, the container console is working again for me!

Thanks!

 

[alazir]

@dcsapak Thank you for an advise! I have faced with it today too. It works now

 

[krikey]

this worked for me too. Thank you.

 

[fantaxp7]

Hi I'm getting an issue just like this. Is there a bug fix?

 

[sb-jw]

Did you already updated your Nodes to the latest version? If not, try this first.

 

[fantaxp7]

Did you already updated your Nodes to the latest version? If not, try this first.

Hello,

Yes I did, as mentioned above. I noticed my web ui update to "Virtual Environment 5.3-8" from 5.3-7 after doing the above.

Thanks