-
-
Save charlyie/76ff7d288165c7d42e5ef7d304245916 to your computer and use it in GitHub Desktop.
| # If Debian 11 is ran on a LXC container (Proxmox), SSH login and sudo actions can be slow | |
| # Check if in /var/log/auth.log the following messages | |
| Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms) | |
| -> Run systemctl mask systemd-logind | |
| -> Run pam-auth-update (and deselect Register user sessions in the systemd control group hierarchy) |
Thanks!
From https://jrs-s.net/2017/07/01/slow-ssh-logins/ it seems this does the same thing. I would love if you could explain why that is.
Still experiencing this issue. Thanks for your gist!
Saved me some headaches thanks!
Thank you!
Thanks! Solved my issue as well.
Solved for me as well
Thanks for this workaround, works like a charm!
This seems to be a much better solution: https://forum.proxmox.com/threads/lxc-container-upgrade-to-bullseye-slow-login-and-apparmor-errors.93064/
Basically there is no need to mask the systemd-logind service. Just turn on "nesting" in proxmox.
I was having this issue with Debian 12, this solved the issue. Thanks!
Basically there is no need to mask the systemd-logind service. Just turn on "nesting" in proxmox.
It's not possible to enable nesting in privileged containers though.
Thanks! It also helps with LXD containers!
Thank you my lord
Thanks! Its helped me.
This seems to be a much better solution: https://forum.proxmox.com/threads/lxc-container-upgrade-to-bullseye-slow-login-and-apparmor-errors.93064/
Basically there is no need to mask the systemd-logind service. Just turn on "nesting" in proxmox.
100% correct. However sometimes you do not want nesting on so this is not a "better" solution - just another one. I use both.
Good, Thans!
So glad I stumbled on this... During my upgrades, I had let dpkg replace my custom sshd_config with the stock one, so get fooled into thinking it was related to that. This fixed it.
Edit:
For anyone looking to do the pam-auth-update in a non-interactive way.... Use this:
"pam-auth-update --remove systemd"
I've now encountered this because i have to use a privileged container with debian 12. Unfortunately, this solution here prevents things like systemctl poweroff from working.
Fortunately, L1Cafe's link offers a better solution:
Comment out session optional pam_systemd.so in /etc/pam.d/common-session
This seems to solve the issue while keeping systemd-logind intact (haven't done much testing though!)
it works, thank you
This fixed my problem, thank you.
It's not possible to enable nesting in privileged containers though.
It's possible to turn on nesting after container creation: CT |-> Options |-> Features |-> Edit
Thanks! 🤗
Nice.