Arch Linux

bernd_b

Member

Registered: 2013-07-30

Posts: 183

[solved] What makes systemd-logind.service fail?

After last update made yesterday I was unable to reboot. With the help of an installation cd  and chrooting I disabled my graphical login manager lxdm which, when started, seems to do nothing and the system is stuck.

Without lxdm service enabled, I can start xfce4 with

startxfce4

from commandline and everything seems to run fine. 

But the booting process gives me several messages telling that the service systemd-logind failed. Apart from the virtual console created while booting and the one running X11 there is no other one (no login prompt when pressing strg+alt f3 e.g.)

[root@amd64-archlinux ~]# systemctl status systemd-logind
● systemd-logind.service - Login Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
   Active: failed (Result: start-limit) since Sun 2014-06-08 19:09:24 CEST; 5min 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
  Process: 336 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
 Main PID: 336 (code=exited, status=1/FAILURE)
   Status: "Shutting down..."

Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.
Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Stopping Login Service...
Jun 08 19:09:24 amd64-archlinux systemd[1]: Starting Login Service...
Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.

Has anyone an idea where to lead me?

Last edited by bernd_b (2014-06-09 11:20:21)

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [solved] What makes systemd-logind.service fail?

Why are you not using ~/.xinitrc with startx?

bernd_b

Member

Registered: 2013-07-30

Posts: 183

Re: [solved] What makes systemd-logind.service fail?

How does this clarify why the systemd-logind service fails?

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [solved] What makes systemd-logind.service fail?

How does this clarify why the systemd-logind service fails?

I don't know that it does necessarily.  But logind tracks your session, so using startx does some basic things to properly keep your session in tact.  I'm not sure that this is your issue, but doing things properly wouldn't hurt.

If you only log into the getty@tty1, does systemd-logind still report a failure at that point?

bernd_b

Member

Registered: 2013-07-30

Posts: 183

Re: [solved] What makes systemd-logind.service fail?

I don't know if I got you point - but here is a try:

I am running X11 started manually with "startxfce4". So firing up a konsole in X11 I do and get

root@amd64-archlinux pkg]# systemctl stop systemd-logind
[root@amd64-archlinux pkg]# systemctl start systemd-logind
Job for systemd-logind.service failed. See 'systemctl status systemd-logind.service' and 'journalctl -xn' for details.

journalctl -xn:

-- Unit systemd-logind.service has begun shutting down.
Jun 08 21:38:18 amd64-archlinux systemd[1]: Starting Login Service...
-- Subject: Unit systemd-logind.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-logind.service has begun starting up.
Jun 08 21:38:18 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
Jun 08 21:38:18 amd64-archlinux systemd[1]: Failed to start Login Service.
-- Subject: Unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-logind.service has failed.
-- 
-- The result is failed.

I ran the service directly I get:

[root@amd64-archlinux pkg]# /usr/lib/systemd/systemd-logind 
Failed to connect to system bus: No such file or directory
Failed to fully start up daemon: No such file or directory

What I figured out so far is this in addition:
- krusader does not start- there is no response or message in the konsole when firing up this application.
- I can only mount nfs-shares with the option "-o nolock" otherwise I get, e.g.

mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified

Last edited by bernd_b (2014-06-08 19:48:43)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: [solved] What makes systemd-logind.service fail?

Not an Installation issue, moving to Apps & DEs...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

bernd_b

Member

Registered: 2013-07-30

Posts: 183

Re: [solved] What makes systemd-logind.service fail?

O.K, this seems to be somewhat solved:
After down and upgrading this and that I fetched some hints (=error messages) of "/var/lib/systemd" not being available.

Of course it was available, but /var directory was a symbolic link to another partition. So maybe not available soon enough any more at boot time?

However:
Copying back the whole /var directory to the root partition (still leaving out the biggest subdirectoy "cache" by still using a symbolic link to an other partition) brought normal behaviour back.
No error messages on boot any more and lxdm working again.

Thanks once again for watching and moving.

Last edited by bernd_b (2014-06-09 11:20:56)