Cannot login: Failed to start Login Service
I’ve got a VirtualBox instance of Oracle Linux 7.2 which won’t start because of Failed to start Login Service . On the booting sequence the process hangs on this message and doesn’t continue, so I can’t even log in and execute systemctl status systemd-logind.service .
The probable cause for this is, that I removed zsh while all my users (including root) have zsh set as the default shell (duh!). After that the machine started and I got to the login prompt, but I couldn’t login since the shell couldn’t be found. I then inserted a Live CD and went into /etc/passwd to change the default shell for users to /bin/bash . After this the login service won’t start at all. Any ideas how to fix this?
3 Answers 3
I found out that after changing /etc/passwd it didn’t have the right SELinux settings anymore. I don’t really need SELinux on my machine so I solved the problem by disabling SELinux altogether. This is easily done by modifying the file /etc/selinux/config and setting the option SELINUX=permissive (if you want to keep SELinux file labeling to enable it later) or SELINUX=disabled (turning it off completely).
Thread: [FAILED] Failed to start Login Service — On boot Leap 42.1
Thread Tools
Display
[FAILED] Failed to start Login Service — On boot Leap 42.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.
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.
Last edited by malcolmlewis; 18-May-2017 at 08:29 . Reason: Update prefix as 42.1 is EOL
Re: [FAILED] Failed to start Login Service — On boot Leap 42.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.
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.
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.
Не стартует logind
Ставлю стабилизировавшийся systemd по wiki. Пересобрал мир с глобальным юзом. При загрузке не стартуют logind и networkmanager.
Команда systemctl от пользователя выдает:
Ставил точно также, все нормально.
selinux не включен случаем?
Нет. Профиль desktop/kde
Беда происходит на ноуте со всеми зашифрованными разделами, включая root. Initramfs собирал когда-то давно по статье отсюда. Недавно лишь поменял переменную uv_init, чтоб указывала на systemd.
Но ведь это не должно влиять, не так ли?
должно. У тебя dbus в initrd есть? Пользуй dracut шоб initrd генерить.
Dracut помог. Благодарю!
у вас только с dbus в initrd запустилось?
бред, но из initrd’a запускается openrc и дальше сервисы в системе.
у меня сейчас вот что говорит:
root# systemctl status
Failed to get D-Bus connection: No connection to service manager.
Arch Linux
You are not logged in.
#1 2015-01-10 03:05:14
[SOLVED] systemd-logind.service failed
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:
The ouput of journalctl _PID=403 is:
I tried to reinstall systemd + reboot — no luck.
I tried
+ reboot — no luck.
I tried
+ reboot — no luck. Strangely it still loads after reboot.
I tried
+ 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)
#2 2015-01-10 03:10:27
Re: [SOLVED] systemd-logind.service failed
+ 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)
#3 2015-01-10 03:14:09
Re: [SOLVED] systemd-logind.service failed
Registered Linux User #482438
#4 2015-01-10 03:37:13
Re: [SOLVED] systemd-logind.service failed
@jasomwryan:
Just finished reading it. am not sure what part you are referring to but if I have violated in some way I apologize.
#5 2015-01-10 03:40:25
Re: [SOLVED] systemd-logind.service failed
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.
Registered Linux User #482438
#6 2015-01-10 04:03:50
Re: [SOLVED] systemd-logind.service failed
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.
#7 2015-01-10 04:09:55
Re: [SOLVED] systemd-logind.service failed
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?
Registered Linux User #482438
#8 2015-01-10 04:29:49
Re: [SOLVED] systemd-logind.service failed
to .xinitrc
Then I placed
/.zlogin
No greeter or display manager installed.
Openbox works without a problem.
#9 2015-01-10 04:57:39
Re: [SOLVED] systemd-logind.service failed
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:
Registered Linux User #482438
#10 2015-01-10 17:28:04
Re: [SOLVED] systemd-logind.service failed
The above command returns
#11 2015-01-10 18:00:12
Re: [SOLVED] systemd-logind.service failed
Registered Linux User #482438
#12 2015-01-10 21:56:20
Re: [SOLVED] systemd-logind.service failed
As the article you referenced instructs, I replaced
But now when I login it does not start openbox.
I have to manually type
#13 2015-01-10 22:12:22
Re: [SOLVED] systemd-logind.service failed
But now when I login it does not start openbox.
Registered Linux User #482438
#14 2015-01-11 00:42:47
Re: [SOLVED] systemd-logind.service failed
Ok. So I unmasked the systemd-logind service as you suggested and rebooted.
The service failed like before.
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?
#15 2015-01-11 00:53:10
Re: [SOLVED] systemd-logind.service failed
The Xorg log looks OK.
Try using this in your profile:
Also, please paste your .xinitrc.
Registered Linux User #482438
#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
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?
Registered Linux User #482438
#18 2015-01-11 02:06:51
Re: [SOLVED] systemd-logind.service failed
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
#19 2015-01-11 02:13:49
Re: [SOLVED] systemd-logind.service failed
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.
#20 2015-01-11 02:16:24
Re: [SOLVED] systemd-logind.service failed
That is the .xinitrc configuration recommended by one of the openbox support articles.
Your .xinitrc is broken because it doesn’t start dbus properly (which is why you have logind failures).
Registered Linux User #482438
#21 2015-01-11 03:32:40
Re: [SOLVED] systemd-logind.service failed
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.
#22 2015-01-11 04:30:47
Re: [SOLVED] systemd-logind.service failed
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.
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:
#23 2015-01-11 12:23:52
Re: [SOLVED] systemd-logind.service failed
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)
#24 2015-01-11 15:32:13
Re: [SOLVED] systemd-logind.service failed
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.
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.