[SOLVED] systemd-logind.service failed

rujutsu · 2015-01-11 17:55:33

rebootl wrote:

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

Greetings rebootl. Here is the result:

root:~/ # /usr/lib/systemd/systemd-logind                                                                                                  [2:24:20]
Failed to connect to system bus: No such file or directory
Failed to fully start up daemon: No such file or directory

journalctl -xe (after above command)

root:~/ # systemctl --failed                                                                                                              [12:56:57]
  UNIT                   LOAD   ACTIVE SUB    DESCRIPTION
● systemd-logind.service loaded failed failed Login Service

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

root:~/ # systemctl status dbus.socket                                                                                                    [12:57:04]
● dbus.socket - D-Bus System Message Bus Socket
   Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static; vendor preset: disabled)
   Active: active (running) since Sun 2015-01-11 01:59:43 EST; 10h ago
   Listen: /run/dbus/system_bus_socket (Stream)

root:~/ # systemctl status dbus.service *                                                                                                 [12:57:46]
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
   Active: active (running) since Sun 2015-01-11 01:59:43 EST; 10h ago
     Docs: man:dbus-daemon(1)
 Main PID: 395 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           └─395 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

Jan 11 02:00:21 Katana dbus[395]: [system] Reloaded configuration
Jan 11 02:00:21 Katana dbus[395]: [system] Reloaded configuration
Jan 11 02:00:21 Katana dbus[395]: [system] Reloaded configuration
Jan 11 02:00:21 Katana dbus[395]: [system] Reloaded configuration
Jan 11 02:00:21 Katana dbus[395]: [system] Reloaded configuration
Jan 11 02:00:21 Katana dbus[395]: [system] Reloaded configuration
Jan 11 02:00:21 Katana dbus[395]: [system] Reloaded configuration
Jan 11 02:00:21 Katana dbus[395]: [system] Reloaded configuration
Jan 11 02:00:22 Katana dbus[395]: [system] Failed to activate service 'org.freedesktop.login1': timed out
Jan 11 02:00:22 Katana dbus[395]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out

● boot_msg.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● dead.letter.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● Desktop.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● Downloads.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● journalctl_log.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● journalctl_log2.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● journalctlxe.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

Last edited by rujutsu (2015-01-11 17:59:06)

rujutsu · 2015-01-11 18:03:34

falconindy wrote:

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.

root:~/ # /usr/lib/systemd/systemd-logind SYSTEMD_LOG_LEVEL=debug                                                                         [12:58:39]
This program takes no arguments.

How would I do this?

rujutsu · 2015-01-11 18:07:55

rebootl wrote:

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 ?

pacman.log
Yes my system is up to date

falconindy · 2015-01-11 18:34:11

rujutsu wrote:

falconindy wrote:
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.
root:~/ # /usr/lib/systemd/systemd-logind SYSTEMD_LOG_LEVEL=debug                                                                         [12:58:39]
This program takes no arguments.
How would I do this?

Prefix it, not suffix, like I said to.

$ SYSTEMD_LOG_LEVEL=debug /usr/lib/systemd/systemd-logind

You have larger problems than logind not starting up, though. Your /run/dbus/system_bus_socket doesn't exist, which is what causes logind to fail to start. As a wild guess, is your /var/run not a symlink to /run?

rujutsu · 2015-01-11 18:54:47

falconindy wrote:

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

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.
root:~/ # /usr/lib/systemd/systemd-logind SYSTEMD_LOG_LEVEL=debug                                                                         [12:58:39]
This program takes no arguments.
How would I do this?
Prefix it, not suffix, like I said to.
$ SYSTEMD_LOG_LEVEL=debug /usr/lib/systemd/systemd-logind
You have larger problems than logind not starting up, though. Your /run/dbus/system_bus_socket doesn't exist, which is what causes logind to fail to start. As a wild guess, is your /var/run not a symlink to /run?

SYSTEMD_LOG_LEVEL=debug /usr/lib/systemd/systemd-logind    [13:52:15]
Failed to connect to system bus: No such file or directory
Failed to fully start up daemon: No such file or directory

Also, as a sidenote, I tried installing LXDM in hopes that it would automatically remedy the problem. It didn't.

How would I check that symlink?

falconindy · 2015-01-11 19:00:13

Are you familiar with the "ls" command?

rujutsu · 2015-01-11 19:13:20

falconindy wrote:

Are you familiar with the "ls" command?

root:~/ # find /var/run -type l                                      [14:11:35]
root:~/ # find /run -type l                                          [14:11:50]
/run/systemd/generator/local-fs.target.requires/extra.mount
/run/systemd/generator/local-fs.target.requires/backup.mount
/run/systemd/generator/local-fs.target.requires/boot.mount
/run/systemd/generator/local-fs.target.requires/-.mount
/run/systemd/generator/local-fs.target.wants/systemd-fsck-root.service
/run/udev/watch/16
/run/udev/watch/15
/run/udev/watch/14
/run/udev/watch/13
/run/udev/watch/9
/run/udev/watch/8
/run/udev/watch/7
/run/udev/watch/6
/run/udev/watch/5
/run/udev/watch/4
/run/udev/watch/3
/run/udev/watch/2
/run/udev/watch/1
/run/udev/static_node-tags/uaccess/snd\x2fseq
/run/udev/static_node-tags/uaccess/snd\x2ftimer

rebootl · 2015-01-11 19:52:38

I'm not sure about your find output...

Could you please show the output of

$ ls -l /var/run
(and maybe also)
$ ls -l /run/dbus
$ ls -l /var
$ ls -l /
$ mount

falconindy · 2015-01-11 20:00:50

The fact that "find /var/run -type l" doesn't return anything is indicative of exactly the problem I asked about -- /var/run not being a symlink to /run. Reinstalling the filesystem package should fix that.

rujutsu · 2015-01-11 20:33:29

rebootl wrote:

I'm not sure about your find output...
Could you please show the output of
$ ls -l /var/run
(and maybe also)
$ ls -l /run/dbus
$ ls -l /var
$ ls -l /
$ mount

the above commands

rujutsu · 2015-01-11 20:36:43

falconindy wrote:

The fact that "find /var/run -type l" doesn't return anything is indicative of exactly the problem I asked about -- /var/run not being a symlink to /run. Reinstalling the filesystem package should fix that.

root:~/ # pacman -S filesystem                                                                                                            [15:34:36]
warning: filesystem-2014.10-3 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) filesystem-2014.10-3

Total Installed Size:  0.01 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                                            [####################################################] 100%
(1/1) checking package integrity                                                          [####################################################] 100%
(1/1) loading package files                                                               [####################################################] 100%
(1/1) checking for file conflicts                                                         [####################################################] 100%
(1/1) checking available disk space                                                       [####################################################] 100%
(1/1) reinstalling filesystem                                                             [####################################################] 100%
error: extract: not overwriting dir with file /var/run
error: problem occurred while upgrading filesystem
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.

How do I address the above error?

rebootl · 2015-01-11 21:35:01

Ok, then move /var/run/ to /var/run_OLD/ or so, and try again.

rujutsu · 2015-01-11 21:45:02

Ok. So I uninstalled lxdm and deleted the /var/run directory.
Then I was able to reinstall the filesystem package.
I rebooted and there were no more logind error messages.
To verify, I ran systemctl status and indeed all is fixed.

Thanks for all the help guys!
I will be marking this thread as [Solved]

Arch Linux

#26 2015-01-11 17:55:33

Re: [SOLVED] systemd-logind.service failed

#27 2015-01-11 18:03:34

Re: [SOLVED] systemd-logind.service failed

#28 2015-01-11 18:07:55

Re: [SOLVED] systemd-logind.service failed

#29 2015-01-11 18:34:11

Re: [SOLVED] systemd-logind.service failed

#30 2015-01-11 18:54:47

Re: [SOLVED] systemd-logind.service failed

#31 2015-01-11 19:00:13

Re: [SOLVED] systemd-logind.service failed

#32 2015-01-11 19:13:20

Re: [SOLVED] systemd-logind.service failed

#33 2015-01-11 19:52:38

Re: [SOLVED] systemd-logind.service failed

#34 2015-01-11 20:00:50

Re: [SOLVED] systemd-logind.service failed

#35 2015-01-11 20:33:29

Re: [SOLVED] systemd-logind.service failed

#36 2015-01-11 20:36:43

Re: [SOLVED] systemd-logind.service failed

#37 2015-01-11 21:35:01

Re: [SOLVED] systemd-logind.service failed

#38 2015-01-11 21:45:02

Re: [SOLVED] systemd-logind.service failed

Board footer