[SOLVED] systemd-logind.service failed

rujutsu · 2015-01-10 03:05:14

What's up guys!
I checked the wiki and searched the forum + google but I can't seem to find an answer to this darn puzzle.
DISCLAIMER: I am new to linux so please be patient with me.

My system was working fine and all of a sudden I get this error in startup:
systemd-logind.service failed

output of "systemctl status systemd-logind.service" is:

root:~/ # systemctl status systemd-logind.service                                                                                         
● systemd-logind.service - Login Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled)
   Active: failed (Result: start-limit) since Fri 2015-01-09 21:21:40 EST; 28min ago
     Docs: man:systemd-logind.service(8)
           man:logind.conf(5)
           [url]http://www.freedesktop.org/wiki/Software/systemd/logind[/url]
           [url]http://www.freedesktop.org/wiki/Software/systemd/multiseat[/url]
  Process: 403 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
 Main PID: 403 (code=exited, status=1/FAILURE)
   Status: "Shutting down..."

Jan 09 21:21:40 Katana systemd[1]: Failed to start Login Service.
Jan 09 21:21:40 Katana systemd[1]: Unit systemd-logind.service entered failed state.
Jan 09 21:21:40 Katana systemd[1]: systemd-logind.service failed.
Jan 09 21:21:40 Katana systemd[1]: start request repeated too quickly for systemd-logind.service
Jan 09 21:21:40 Katana systemd[1]: Failed to start Login Service.
Jan 09 21:21:40 Katana systemd[1]: Unit systemd-logind.service entered failed state.
Jan 09 21:21:40 Katana systemd[1]: systemd-logind.service failed.

The ouput of journalctl _PID=403 is:

root:~/ # journalctl _PID=403                                                                                                             [21:50:19]
-- Logs begin at Mon 2015-01-05 20:58:15 EST, end at Fri 2015-01-09 21:26:07 EST. --
Jan 09 05:16:22 Katana systemd-logind[403]: Failed to connect to system bus: No such file or directory
Jan 09 05:16:22 Katana systemd-logind[403]: Failed to fully start up daemon: No such file or directory
-- Reboot --
Jan 09 06:35:39 Katana systemd-logind[403]: Failed to connect to system bus: No such file or directory
Jan 09 06:35:39 Katana systemd-logind[403]: Failed to fully start up daemon: No such file or directory
-- Reboot --
Jan 09 21:21:40 Katana systemd-logind[403]: Failed to connect to system bus: No such file or directory
Jan 09 21:21:40 Katana systemd-logind[403]: Failed to fully start up daemon: No such file or directory

I tried to reinstall systemd + reboot - no luck.
I tried

mkinitcpio -p linux

+ reboot - no luck.
I tried

systemctl disable systemd-logind.service

+ reboot - no luck. Strangely it still loads after reboot.
I tried

systemctl disable systemd-logind

+ reboot - no luck. Strangely it still loads after reboot.

My system seems to be running normally otherwise so I don't know if this can be ignored, but I'd rather have an error-free system...
Any suggestions would be greatly appreciated. Thank you in advance for your time and concern!

Last edited by rujutsu (2015-01-11 21:46:02)

rujutsu · 2015-01-10 03:10:27

UPDATE:
I ran

systemctl mask systemd-logind.service

+ reboot and the problem is solved!
However, is there a real way to fix this without just disabling the service?
Thanks!

Last edited by rujutsu (2015-01-10 04:21:26)

jasonwryan · 2015-01-10 03:14:09

Please read the Forum Etiquette, notably https://wiki.archlinux.org/index.php/Fo … ow_to_Post

rujutsu · 2015-01-10 03:37:13

@jasomwryan:
Just finished reading it...am not sure what part you are referring to but if I have violated in some way I apologize.

jasonwryan · 2015-01-10 03:40:25

Your title: the All Caps plea for HELP!!! for a start. Use code tags when pasting to the boards.

Then please include details of your steup: how you login, into what, etc...

rujutsu · 2015-01-10 04:03:50

Oh ok...Once again, my apologies.

I am running Linux 3.17.6-1-ARCH with Openbox 3.5.2 and Zsh 5.0.7.

jasonwryan · 2015-01-10 04:09:55

Stop apologising and just edit your posts and fix the things I asked you to.

How do you login? Do you have a greeter or display manager? Do you have an active session?

rujutsu · 2015-01-10 04:29:49

I have added

exec openbox-session

to .xinitrc
Then I placed

startx

in the ~/.zlogin
No greeter or display manager installed.
Openbox works without a problem.

jasonwryan · 2015-01-10 04:57:39

Read `man systemd-logind`: you don't want to mask this service without good reason. That is why I was asking if you had an active session:

loginctl show-session $XDG_SESSION_ID

rujutsu · 2015-01-10 17:28:04

The above command returns

Failed to create bus connection: No such file or directory

jasonwryan · 2015-01-10 18:00:12

https://wiki.archlinux.org/index.php/Start_X_at_login

rujutsu · 2015-01-10 21:56:20

As the article you referenced instructs, I replaced

startx

in the ~/.zlogin file with

[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx

But now when I login it does not start openbox.
I have to manually type

startx

to start openbox.

jasonwryan · 2015-01-10 22:12:22

rujutsu wrote:

But now when I login it does not start openbox.

Why not? https://bbs.archlinux.org/viewtopic.php?id=57855

rujutsu · 2015-01-11 00:42:47

Ok. So I unmasked the systemd-logind service as you suggested and rebooted.
The service failed like before.

root:~/ # systemctl status systemd-logind                                                                                                 [19:39:29]
● systemd-logind.service - Login Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled)
   Active: failed (Result: start-limit) since Sat 2015-01-10 19:15:33 EST; 24min 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: 392 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
 Main PID: 392 (code=exited, status=1/FAILURE)
   Status: "Shutting down..."

Jan 10 19:15:33 Katana systemd[1]: Failed to start Login Service.
Jan 10 19:15:33 Katana systemd[1]: Unit systemd-logind.service entered failed state.
Jan 10 19:15:33 Katana systemd[1]: systemd-logind.service failed.
Jan 10 19:15:33 Katana systemd[1]: start request repeated too quickly for systemd-logind.service
Jan 10 19:15:33 Katana systemd[1]: Failed to start Login Service.
Jan 10 19:15:33 Katana systemd[1]: Unit systemd-logind.service entered failed state.
Jan 10 19:15:33 Katana systemd[1]: systemd-logind.service failed.

And upon login, it still does not autostart openbox.
Here's the output of dmesg
Here's the output of /var/log/Xorg.0.log

Is there another log file I should be showing you?

jasonwryan · 2015-01-11 00:53:10

The Xorg log looks OK.

Try using this in your profile:

[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx -- vt1 -keeptty

Also, please paste your .xinitrc.

rujutsu · 2015-01-11 01:34:15

Openbox is still not auto-starting. Here is:
journalctl before above change
journalctl after above change

...and .xinitrc is

DISPLAY=:0.1 openbox &
exec openbox-session

jasonwryan · 2015-01-11 01:48:22

That is wrong.

Why didn't you copy the one from /etc/skel as advised here: https://wiki.archlinux.org/index.php/Xinitrc

And why are you starting openbox twice?

And exporting DISPLAY?

rujutsu · 2015-01-11 02:06:51

That is the .xinitrc configuration recommended by one of the openbox support articles.
I have 2 monitors set up as 2 separate x screens.
xorg.conf

rujutsu · 2015-01-11 02:13:49

For the purpose of troubleshooting this problem, I have reverted my .xinitrc to the one in /etc/skel and rebooted.
However, it didn't change anything.

jasonwryan · 2015-01-11 02:16:24

rujutsu wrote:

That is the .xinitrc configuration recommended by one of the openbox support articles.

Link?

Your .xinitrc is broken because it doesn't start dbus properly (which is why you have logind failures).

falconindy · 2015-01-11 03:32:40

Logind runs on the system bus, not the user bus you're suggesting he needs to start.

I would start logind manually to see why it fails...

rujutsu · 2015-01-11 04:30:47

jasonwryan wrote:

Link?
Your .xinitrc is broken because it doesn't start dbus properly (which is why you have logind failures).

I do not have the link - it was a while ago.
My .xinitrc is fine now since I copied it from /etc/skel but I'm still having the systemd-logind problem.

falconindy wrote:

Logind runs on the system bus, not the user bus you're suggesting he needs to start.
I would start logind manually to see why it fails...

Greetings falconindy. Here is the result:

root:~/ # systemctl start systemd-logind                             [21:14:30]
Job for systemd-logind.service failed. See "systemctl status systemd-logind.service" and "journalctl -xe" for details.

rebootl · 2015-01-11 12:23:52

I'm not sure but by 'starting manually' maybe it was meant to use the command '/usr/lib/systemd/systemd-logind' directly (?).

Also after you execute the systemctl command above it suggests to use "journalctl -xe", have you tried this/ what's its output (do it right after you enter the above command) ?

And also, do you have other failed units ('systemctl --failed') ?
And if I understand correctly it seems to be a problem with dbus. What's the output of 'systemctl status dbus.socket' and 'systemctl status dbus.service' * ?

* Edit: "status" was missing here

Last edited by rebootl (2015-01-11 13:30:41)

falconindy · 2015-01-11 15:32:13

rebootl wrote:

I'm not sure but by 'starting manually' maybe it was meant to use the command '/usr/lib/systemd/systemd-logind' directly (?).

Yes, that's what I meant. If needed, raise loglevel by prefixing the command with SYSTEMD_LOG_LEVEL=debug.

rebootl wrote:

And if I understand correctly it seems to be a problem with dbus. What's the output of 'systemctl status dbus.socket' and 'systemctl status dbus.service' * ?

There's no evidence that this is a dbus issue because the OP hasn't been able to provide the reason that logind is failing.

rebootl · 2015-01-11 17:06:03

Thanks for clarifying, falconindy.

Also going back to the opening post, you (rujutsu) said "all of a sudden".
This is somewhat unlikely. Did it maybe start after an update or package install ? Re-check your pacman.log, evtl. provide the part of the last update here + is your system up to date ?

Arch Linux

#1 2015-01-10 03:05:14

[SOLVED] systemd-logind.service failed

#2 2015-01-10 03:10:27

Re: [SOLVED] systemd-logind.service failed

#3 2015-01-10 03:14:09

Re: [SOLVED] systemd-logind.service failed

#4 2015-01-10 03:37:13

Re: [SOLVED] systemd-logind.service failed

#5 2015-01-10 03:40:25

Re: [SOLVED] systemd-logind.service failed

#6 2015-01-10 04:03:50

Re: [SOLVED] systemd-logind.service failed

#7 2015-01-10 04:09:55

Re: [SOLVED] systemd-logind.service failed

#8 2015-01-10 04:29:49

Re: [SOLVED] systemd-logind.service failed

#9 2015-01-10 04:57:39

Re: [SOLVED] systemd-logind.service failed

#10 2015-01-10 17:28:04

Re: [SOLVED] systemd-logind.service failed

#11 2015-01-10 18:00:12

Re: [SOLVED] systemd-logind.service failed

#12 2015-01-10 21:56:20

Re: [SOLVED] systemd-logind.service failed

#13 2015-01-10 22:12:22

Re: [SOLVED] systemd-logind.service failed

#14 2015-01-11 00:42:47

Re: [SOLVED] systemd-logind.service failed

#15 2015-01-11 00:53:10

Re: [SOLVED] systemd-logind.service failed

#16 2015-01-11 01:34:15

Re: [SOLVED] systemd-logind.service failed

#17 2015-01-11 01:48:22

Re: [SOLVED] systemd-logind.service failed

#18 2015-01-11 02:06:51

Re: [SOLVED] systemd-logind.service failed

#19 2015-01-11 02:13:49

Re: [SOLVED] systemd-logind.service failed

#20 2015-01-11 02:16:24

Re: [SOLVED] systemd-logind.service failed

#21 2015-01-11 03:32:40

Re: [SOLVED] systemd-logind.service failed

#22 2015-01-11 04:30:47

Re: [SOLVED] systemd-logind.service failed

#23 2015-01-11 12:23:52

Re: [SOLVED] systemd-logind.service failed

#24 2015-01-11 15:32:13

Re: [SOLVED] systemd-logind.service failed

#25 2015-01-11 17:06:03

Re: [SOLVED] systemd-logind.service failed

Board footer