You are not logged in.
Hi!
Lately i discovered, that executing `systemctl --user` as an user or as root on my headless server yields:
Failed to connect to bus: No such file or directory
The same with `busctl --user`. `busctl` on its own runs fine.
While stepping deeper into the problem i noticed that `systemctl start user@username` would generate following error:
Dec 16 22:25:54 jarvis systemd[6430]: Failed to create generator directory /run/user/1000/systemd/generator: Permission denied
Dec 16 22:25:54 jarvis systemd[6430]: Failed to fully start up daemon: Permission denied
Dec 16 22:25:54 jarvis systemd[6430]: Failed to load default target: No such file or directory
Dec 16 22:25:54 jarvis systemd[6431]: pam_unix(systemd-user:session): session closed for user nuke
Dec 16 22:25:54 jarvis systemd[6430]: Trying to load rescue target...
Dec 16 22:25:54 jarvis systemd[6430]: Failed to load rescue target: No such file or directory
Dec 16 22:25:54 jarvis systemd[1]: Started User Manager for UID username.
An ls in /run/user/ showed me that the directory was empty.
I didn't see any other errors in my logs. Maybe I'm missing something.
Did anyone encounter a similar issue or can point me in the right direction?
Dmesg output, just in case:
http://pastebin.com/9Nwad4PF
If you need more logs or command outputs, just say it, I will deliver as fast as possible.
Edit:
I stumbled upon another issue. It looks like there are no XDG Variables defined. There is only $XDG_DESKTOP_DIR=/root/
The other variables are missing:
- XDG_RUNTIME_DIR
- XDG_SEAT
- XDG_SESSION_ID
- XDG_VTNR
Last edited by Nukesor (2015-12-17 22:15:32)
Offline
Hi,
Not very helpful but the missing XDG_* variables and systemd-vconsole-setup.service failing to start according to your dmesg make me think you haven't got a fully functioning systemd-logind session. The best I can suggest is having another read of the systemd and installation guide pages of the wiki and seeing how your system compares.
Offline