systemd-logind.service fails in Debian

1,252 views
Skip to first unread message

Sherman Boyd

unread,
Jan 30, 2015, 5:07:45 PM1/30/15
to beagl...@googlegroups.com
systemctl
...
systemd-logind.service                                                           loaded failed failed        Login Service


Is this normal?

Robert Nelson

unread,
Jan 30, 2015, 5:10:23 PM1/30/15
to Beagle Board
Well did you ask systemd about it?

debian@beaglebone:~$ systemctl status -l systemd-logind
● systemd-logind.service - Login Service
Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
Active: active (running) since Fri 2015-01-30 21:06:24 UTC; 1h 2min ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/logind
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Main PID: 267 (systemd-logind)
Status: "Processing requests..."
CGroup: /system.slice/systemd-logind.service
└─267 /lib/systemd/systemd-logind

Jan 30 21:06:24 beaglebone systemd-logind[267]: New seat seat0.
Jan 30 21:06:24 beaglebone systemd-logind[267]: Watching system
buttons on /dev/input/event0 (tps65217_pwr_but)
Jan 30 21:06:30 beaglebone systemd-logind[267]: New session c1 of user debian.
Jan 30 22:08:38 beaglebone systemd-logind[267]: New session c2 of user debian.

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

Sherman Boyd

unread,
Jan 30, 2015, 6:10:49 PM1/30/15
to beagl...@googlegroups.com
I think I have a problem here:

systemctl: invalid option -- 'l'
root@tony:~# systemctl status systemd-logind.service
systemd-logind.service - Login Service
          Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
          Active: failed (Result: exit-code) since Mon, 19 Jan 2015 22:58:59 +0000; 1 weeks and 3 days ago
         Process: 435 ExecStart=/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
          CGroup: name=systemd:/system/systemd-logind.service
Jan 19 22:58:59 tony.xxzzyy.com systemd-logind[435]: Failed to get system D-Bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

Robert Nelson

unread,
Jan 30, 2015, 6:20:34 PM1/30/15
to Beagle Board
On Fri, Jan 30, 2015 at 5:10 PM, Sherman Boyd <sherma...@gmail.com> wrote:
> I think I have a problem here:
>
> systemctl: invalid option -- 'l'
> root@tony:~# systemctl status systemd-logind.service
> systemd-logind.service - Login Service
> Loaded: loaded (/lib/systemd/system/systemd-logind.service;
> static)
> Active: failed (Result: exit-code) since Mon, 19 Jan 2015 22:58:59
> +0000; 1 weeks and 3 days ago
> Process: 435 ExecStart=/lib/systemd/systemd-logind (code=exited,
> status=1/FAILURE)
> CGroup: name=systemd:/system/systemd-logind.service
> Jan 19 22:58:59 tony.xxzzyy.com systemd-logind[435]: Failed to get system
> D-Bus connection: Failed to connect to socket
> /var/run/dbus/system_bus_socket: No such file or directory

See, it looks like your missing: dbus:

sudo apt-get install dbus

Sherman Boyd

unread,
Feb 4, 2015, 12:53:20 PM2/4/15
to beagl...@googlegroups.com
This is a problem with the console version of the Debian image.  I just tried a fresh install of 01/27/2015.  Installing dbus does indeed fix the issue, thank you!
Reply all
Reply to author
Forward
0 new messages