You are not logged in.

#1 2017-07-02 11:26:19

Noroimusha
Member
Registered: 2015-07-23
Posts: 5

systemd-logind.service has failed (+ NetworkManager and 2 other ones)

Hi,
I ran an upgrade with pacman -Syu yesterday and now several services can't start. Switching between consoles won't work, so I can't request the status of systemctl.
The kernel is linux-lts 4.4.11-1 x86_64
The affected services are: systemd-logind.service, NetworkManager, lightdm (already deactivated) and power management daemon.
First of all, posting the pacman log with the complete upgrade:
https://pastebin.com/RYhz4ARd
Then some journalctl -xe:
https://pastebin.com/qE8KHMQc

I've studied these 2 threads but the solutions don't work for me.
https://bbs.archlinux.org/viewtopic.php?id=192053&p=2
https://bbs.archlinux.org/viewtopic.php?id=197881

Offline

#2 2017-07-02 12:25:46

seth
Member
Registered: 2012-09-03
Posts: 51,230

Re: systemd-logind.service has failed (+ NetworkManager and 2 other ones)

I don't see which package update could have caused such, but

Jul 02 12:53:05 Archbook systemd-logind[393]: Failed to enable subscription: Failed to activate service 'org.freedesktop.systemd1': timed out

looks bad enough.


Wild guess: "df -h"?

Offline

#3 2017-07-02 13:43:29

Noroimusha
Member
Registered: 2015-07-23
Posts: 5

Re: systemd-logind.service has failed (+ NetworkManager and 2 other ones)

seth wrote:

I don't see which package update could have caused such, but

Jul 02 12:53:05 Archbook systemd-logind[393]: Failed to enable subscription: Failed to activate service 'org.freedesktop.systemd1': timed out

looks bad enough.


Wild guess: "df -h"?

df -h returns 30 G free space, no issues here.

Offline

#4 2017-07-02 13:57:20

seth
Member
Registered: 2012-09-03
Posts: 51,230

Re: systemd-logind.service has failed (+ NetworkManager and 2 other ones)

Certainly not. There'll be more than one partition.
Either way, that bus dead means game over - the problem goes beyond some services not starting.

dbus-send --print-reply --system  --dest=org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.DBus.Introspectable.Introspect

Should get you a nice xml list of the interface - or an error.

Offline

#5 2017-07-02 15:39:28

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,791

Re: systemd-logind.service has failed (+ NetworkManager and 2 other ones)

No guarantees, but my suggestion would be to boot from the install media, set up and enter a chroot, and do another pacman -Syu (perhaps using a different mirror)
I am thinking there is a possibility that the mirror you had been using was not fully synced at the time you did your update.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#6 2017-07-02 17:20:01

Noroimusha
Member
Registered: 2015-07-23
Posts: 5

Re: systemd-logind.service has failed (+ NetworkManager and 2 other ones)

seth wrote:

Certainly not. There'll be more than one partition.
Either way, that bus dead means game over - the problem goes beyond some services not starting.

dbus-send --print-reply --system  --dest=org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.DBus.Introspectable.Introspect

Should get you a nice xml list of the interface - or an error.

Alright, so this shows me a large xml:
https://pastebin.com/raw/cJymvpGJ
Thanks

Offline

#7 2017-07-02 20:08:37

seth
Member
Registered: 2012-09-03
Posts: 51,230

Re: systemd-logind.service has failed (+ NetworkManager and 2 other ones)

The text isn't important, but the service responds. This is from the broken system, not some install medium, right?
Otoh there's clearly communication problems with the system dbus.

You may try ewaller's suggestion, but systemd hasn't seen updates for quite a while.

Voodoo tactics:
Anything suspicious about your filesystem layout? "Strange" /var or /run mounts? Remote filesystems?
Do you use a stock kernel or eg. the ck kernel (and special IO schedulers) or so?

Offline

#8 2017-07-02 20:57:39

Jäger
Member
Registered: 2017-07-02
Posts: 1

Re: systemd-logind.service has failed (+ NetworkManager and 2 other ones)

Same problem for me to. smile

 (pacman -S $(pacman -Qnq)) 

Fixed it for me.

Last edited by Jäger (2017-07-02 21:32:54)

Offline

#9 2017-07-04 08:02:52

Noroimusha
Member
Registered: 2015-07-23
Posts: 5

Re: systemd-logind.service has failed (+ NetworkManager and 2 other ones)

seth wrote:

The text isn't important, but the service responds. This is from the broken system, not some install medium, right?
Otoh there's clearly communication problems with the system dbus.

You may try ewaller's suggestion, but systemd hasn't seen updates for quite a while.

Voodoo tactics:
Anything suspicious about your filesystem layout? "Strange" /var or /run mounts? Remote filesystems?
Do you use a stock kernel or eg. the ck kernel (and special IO schedulers) or so?

This was made from chroot because the system won't log me in. Maybe I can mask the affected services and then it lets me through.

No, everything's pretty standard, there's a regular LTS kernel, but I've compiled it from ABS with CPU type optimizations. It worked for a year or so w/o issues.

Jäger wrote:

Same problem for me to. smile
(pacman -S $(pacman -Qnq))
Fixed it for me.

I've cleared the package cache (-Scc) and run this command, but the result's still the same.

I'll install the latest kernel and give it a try.

Offline

#10 2017-07-19 14:02:38

luneng8183
Member
Registered: 2014-09-17
Posts: 2

Re: systemd-logind.service has failed (+ NetworkManager and 2 other ones)

Same issue here, boot will stuck but will eventually show you the login prompt, taking long time.

re-installing all packages does not solve the problem.

Offline

Board footer

Powered by FluxBB