On 25.12.2022 19:23, mh@mike.franken.de wrote:
The only way I can reproduce your error is
1. There is already systemd user instance running (at least, /run/users/$UID/systemd exists)
exists
2. There is no default session dbus socket (/run/users/$UID/bus) which is already something that should not happen - it is created automatically by systemd user instance.
doesn't exist
That is enough to reproduce the problem. So this is the main reason. Did you try to reboot your server? Do you still observe the problem after reboot?
3. sshd PAM configuration does not use pam_systemd
how can I check this?
It is red herring, the root cause is the missing D-Bus socket.
4. Something sets manually XDG_RUNTIME_DIR
I have no idea how you can get into this situation. Check mentioned files/directories. As you refused to show environment, we also do not know whether XDG_RUNTIME_DIR is set and to which value.
echo $XDG_RUNTIME_DIR /run/user/10000