[FAILED] Failed to start Login Service - On boot Leap 42.1

English Install/Boot/Login
1

Hi folks,
I recently had a problem with my btrfs partition for lack of space. The machine could not start at all.
So I used a live cd to create another btrfs partition and add to the existing partition.
After the step, I could use the disc normally.
But now I can not boot the system. The boot stops in login service at boot time.

The boot stops at:

[FAILED] Failed to start Login Service
See "systemctl status systemd-logind.service" for details.

But after this message, I ain’t able to use a console to run the command.
In another topic, I read that “systemctl mask systemd-logind.service” was fixed the problem. But, how can I run this if I cant see a console?
I am using OpenSuse Leap 42.1.

Thanks advance.

2

I do different things to free up space, and if that’s the issue usually I can login. Typically, I only have to free up approx 30MB of free space to allow a bootup, even it’s slow.

First, as you’ve done mount the system drive in a LiveCD to gain access to the file system.

  1. Clear out all files in all temporary files folders(nowadays less likely since these folders are now mounted in RAM, but still take a look at folders like /var/.
  2. Usually I have 10s of megabytes, sometimes over 100MB of files I can delete on the system drive, typically in /opt .

After I’m able to boot into the system, if my root partition is BTRFS, then I immediately run snapper and delete all unnecessary snapshots.

TSU

3

Thanks for the help, but the problem of space I decided.
Now I can not access by a problem in the login service. So I think that they are different issues.
Thank you again.

4

I think the English went wrong in my last answer.
I’m still having problems because I can not start the machine.
The operating system boots stops in the following message:

[FAILED] Failed to start Login Service
See "systemctl status systemd-logind.service" for details.

And I can not go to a terminal for reading logs or try to solve the problem.
How should I proceed?

5

Try boot into single user mode (add s to the end of kernel command line in bootloader); you will get a shell and should be able to check logs.

6

I can’t see a file called menu.lst in /boot/grub2. Where is in Leap 42?

7

Grub2 does not use menu list that is a grub1 thing

8

And how to set boot into single user mode on opensuse leap 42.1?

9

On initial bootloader menu press e' on menu entry, you will be in sort of editor, go to line starting with "linux" or "linuxefi", move to the end and insert s’. Press F10 or Ctrl-X to boot.

10

Thank you a lot… Here the output of systemctl:

# systemctl status systemd-logind
systemd-logind.service - Login Service   Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
   Active: inactive (dead)
     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

P.S.: In single user mode boot I can’t connect to internet.

11

You could try run level 3 rather then 1 since that is terminal with network… If you use NetworkManager then you need to specify available to all users for it to start networks before GUI login.

12

To unify logs. Log systemctl:

# systemctl status systemd-logindsystemd-logind.service - Login Service   Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
   Active: inactive (dead)
     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

Log of journalctl:

#journalctl xn
-- Logs begin at Wed 2015-11-11 17:34:36 BRT, end at Sat 2016-02-13 23:00:11 BRT. --
Feb 13 22:57:41 linux-1hdz systemd-journal[449]: Time spent on flushing to /var is 581.691ms for 807 entries.
Feb 13 22:58:06 linux-1hdz dbus-daemon[783]: Failed to start message bus: Failed to open "/etc/dbus-1/system.conf": No such file or directory
Feb 13 22:58:31 linux-1hdz systemd-logind[782]: Failed to fully start up daemon: Connection timed out
Feb 13 22:58:31 linux-1hdz systemd[1]: Failed to register match for Disconnected message: Connection timed out
Feb 13 22:58:56 linux-1hdz systemd[1]: Failed to register match for Disconnected message: Connection timed out
Feb 13 22:58:56 linux-1hdz dbus-daemon[786]: Failed to start message bus: Failed to open "/etc/dbus-1/system.conf": No such file or directory
Feb 13 22:59:46 linux-1hdz systemd[1]: Failed to register match for Disconnected message: Connection timed out
Feb 13 22:59:46 linux-1hdz dbus-daemon[791]: Failed to start message bus: Failed to open "/etc/dbus-1/system.conf": No such file or directory
Feb 13 23:00:11 linux-1hdz systemd-logind[790]: Failed to fully start up daemon: Connection timed out
Feb 13 23:00:11 linux-1hdz systemd[1]: Failed to register match for Disconnected message: Connection timed out
13

Hello :frowning:

14

I haven’t read the whole thread now, but this definitely doesn’t look good:

I would suggest to reinstall the dbus-1 package:

zypper in -f dbus-1
15

The machine can’t access internet.

16

Well, then download the package on another machine, transfer it over (via an USB stick e.g.), and install it manually with zypper (“zypper in -f dbus-1-1.8.16-5.9.x86_64.rpm”) or rpm (“rpm -i --force dbus-1-1.8.16-5.9.x86_64.rpm”).

http://download.opensuse.org/distribution/leap/42.1/repo/oss/suse/x86_64/dbus-1-1.8.16-5.9.x86_64.rpm

17

In attempting installation, I received the following error/message:

/sbin/ldconfig:warning ignoring configuration file that cannot be opened: /etc/ld.so.conf - No such file or directory
18

That’s only a warning.
But you really should have a /etc/ld.so.conf.

Maybe reinstall glibc as well.
http://download.opensuse.org/update/leap/42.1/oss/x86_64/glibc-2.19-19.1.x86_64.rpm

But probably the best would be to install the system from scratch (or upgrade it, maybe even to the same version). You seem to miss vital files, and there are probably missing more still.

19

This error can occur on 42.1 as well as on 42.2 (and I guess the coming 42.3).
The most likely root cause, is a change in UID for a given login name (often to sync up multiple system).

Correction:

  • boot in single user mode (obviously you are root in that mode)
  • delete the /tmp content
    rm -rf /tmp/*
  • force the correct new UID on all files in the home dir
    chmod -r loginName /home/loginName
  • reboot