Console redirection not working across nodes

May 28, 2020
37
10
28
44
South Africa
Hi all

I have been struggling to resolve this issue for ages and was hoping you guys might have some insight.

9 node cluster running PVE7

Console redirection works fine if you logged into the node hosting the workload BUT not working across nodes.

This is what I see in the syslog:

Jul 24 16:46:11 proxmox-host-08 systemd-logind[4206]: New session 91 of user root.
Jul 24 16:46:11 proxmox-host-08 systemd[1]: Started Session 91 of user root.
Jul 24 16:46:12 proxmox-host-08 sshd[3851716]: Received disconnect from IP port 50504:11: disconnected by user <-- I think this is the issue
Jul 24 16:46:12 proxmox-host-08 sshd[3851716]: Disconnected from user root IP port 50504
Jul 24 16:46:12 proxmox-host-08 sshd[3851716]: pam_unix(sshd:session): session closed for user root
Jul 24 16:46:12 proxmox-host-08 systemd-logind[4206]: Session 90 logged out. Waiting for processes to exit.
Jul 24 16:46:12 proxmox-host-08 systemd[1]: session-90.scope: Succeeded.
Jul 24 16:46:12 proxmox-host-08 systemd[1]: session-90.scope: Consumed 1.343s CPU time.
Jul 24 16:46:12 proxmox-host-08 systemd-logind[4206]: Removed session 90.
Jul 24 16:46:12 proxmox-host-08 pmxcfs[4973]: [status] notice: received log
Jul 24 16:46:13 proxmox-host-08 sshd[3851727]: Received disconnect from IP port 50516:11: disconnected by user
Jul 24 16:46:13 proxmox-host-08 sshd[3851727]: Disconnected from user root IP port 50516
Jul 24 16:46:13 proxmox-host-08 sshd[3851727]: pam_unix(sshd:session): session closed for user root
Jul 24 16:46:13 proxmox-host-08 systemd[1]: session-91.scope: Succeeded.
Jul 24 16:46:13 proxmox-host-08 systemd[1]: session-91.scope: Consumed 1.366s CPU time.
Jul 24 16:46:13 proxmox-host-08 systemd-logind[4206]: Session 91 logged out. Waiting for processes to exit.
Jul 24 16:46:13 proxmox-host-08 systemd-logind[4206]: Removed session 91.

As suggested in other threads on similar issues:

I have dbl checked and confirmed permissions for /etc/ is set to 755 for all nodes

I have dbl checked and confirmed pub keys for all nodes loaded across all nodes and have literally tested every nodes from every other node and it completes handshake successfully and connects every time.

Thoughts on cause of disconnect?

Any input would be greatly appreciated.

Thanks in advance.
 
Did you harden your ssh in any way?
You need root login permitted and allow receiving (and sending) of environment variable LC_PVE_TICKET.
 
Did you harden your ssh in any way? -

No

You need root login permitted and allow receiving (and sending) of environment variable LC_PVE_TICKET -

Can confirm root login permitted & both variables have been set correctly:

lbh@SERVERPC-wsl:/mnt/c/Users/LBH$ ssh root@prox-09
Linux proxmox-host-09 5.11.22-2-pve #1 SMP PVE 5.11.22-4 (Tue, 20 Jul 2021 21:40:02 +0200) 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: Sun Jul 25 08:17:56 2021 from 10.212.134.19
root@proxmox-host-09

root@proxmox-host-09:~# cat /etc/ssh/sshd_config | grep LC_PVE_
AcceptEnv LC_PVE_*
root@proxmox-host-09:~# cat /etc/ssh/ssh_config | grep LC_PVE_
SendEnv LC_PVE_*

Issue still persists :(
 
do you have some custom .bashrc or .profile config or something similar? firewall rules ? different mtu settings?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!