pam_systemd(su:session): Cannot create session: Already running in a session or user slice#10822 Closed ryceementioned this issueDec 28, 2019 XDG_RUNTIME_DIR isn't set forrootuser, logged in viasudoinside SSH sessionnix-community/home-manager#601 ...
The bottom line is, as long as something in your session executes su/sudo that goes through pam_systemd, a new session will not be spawned. See PAMName= inuser@uid.service, this is special-cased in pam_systemd to not spawn a session in (and thus can be used to emulate this effect ...
Bug 2170084-pam_systemd(sudo:session): Cannot create session: Already running in a session or user slice Keywords: Improvement× Reproducer× Triaged× Status:CLOSED ERRATA Alias:None Product:Red Hat Enterprise Linux 8 Component:systemd Version:8.7 ...
"pam_systemd(sudo:session): Failed to connect to system bus: No such file or directory" are logging in /var/log/secure Solution Unverified- UpdatedJune 14 2024 at 12:42 AM- English Issue "pam_systemd(crond:session): Failed to connect to system bus: No such file or directory" are loggi...
45:22 hostname proftpd: pam_systemd(proftpd:session): Failed to connect to system bus: Permission denied Jul 25 15:45:22 hostname proftpd: pam_systemd(proftpd:session): Failed to connect to system bus: Permission denied Jul 25 15:45:22 hostname systemd-logind[393]: Removed session 4002326...
I've noticed a subtle difference between my Pi3 and LIME2 server. The Pi3 starts a XDG_SESSION_ID session, while the LIME2 server doesn't. Pi3 admin@Yroklaus:~ $ sudo systemctl status systemd-logind.service ● systemd-logind.service - Login Service Loaded: loaded (/l...
Dec 31 08:28:10 ip-172-31-36-176 sudo: nrpe : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/check_pm2 -A Dec 31 08:28:10 ip-172-31-36-176 sudo: pam_systemd(sudo:session): Failed to connect to system bus: Permission denied ...
If I try to connect to my proftpd server these errors will be logged in /var/log/auth.log: Dec 29 03:22:38 *** proftpd: pam_unix(proftpd:session): session opened for user *** by (uid=0) Dec 29 03:22:59 *** proftpd: pam_unix(proftpd:session): session opened for u...
No I didn't figured it out, I still have the same messages on my journaltctl every now and then (pam_unix(sudo:auth): conversation failedandpam_systemd(login:session): Failed to release session: Interrupted system call) But at least not every single day as before. ...