1777653 – Silverblue logind not able to start

Bug 1777653 - Silverblue logind not able to start

Summary: Silverblue logind not able to start

Keywords:
Status:	CLOSED CURRENTRELEASE
Alias:	None
Product:	Fedora
Classification:	Fedora
Component:	systemd
Sub Component:
Version:	32
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	unspecified
Target Milestone:	---
Assignee:	systemd-maint
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2019-11-28 01:09 UTC by thiago.frmoraes
Modified:	2021-05-18 17:31 UTC (History)
CC List:	5 users (show)
Fixed In Version:
Clone Of:
Environment:
Last Closed:	2021-05-18 17:31:07 UTC
Type:	Bug
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Description thiago.frmoraes 2019-11-28 01:09:08 UTC

Description of problem:

After updating to the last Silverblue rawhide version (Rawhide.20191127.n.0) the system is not able to start because systemd-logind is not starting.


Version-Release number of selected component (if applicable):

Rawhide.20191127.n.0

How reproducible:


Steps to Reproduce:
1. sudo rpm-ostree update # to update to Rawhide.20191127.n.0 version
2. systemctl reboot
3. wait to start after reboot

Actual results:

Not starting the system

Expected results:

Start the system

Additional info:

This is the output of journalctl -b -1 -u systemd-logind :

-- Logs begin at Tue 2019-10-22 21:12:26 -03, end at Wed 2019-11-27 22:07:26 -03. --
nov 27 21:29:30 silverblue systemd[1]: Starting Login Service...
nov 27 21:29:30 silverblue systemd[795]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/kmsg: Permission denied
nov 27 21:29:30 silverblue systemd[795]: systemd-logind.service: Failed at step NAMESPACE spawning /sbin/modprobe: Permission denied
nov 27 21:29:30 silverblue systemd[796]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/kmsg: Permission denied
nov 27 21:29:30 silverblue systemd[796]: systemd-logind.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-logind: Permission denied
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
nov 27 21:29:30 silverblue systemd[1]: Failed to start Login Service.
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Service has no hold-off time (RestartSec=0), scheduling restart.
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 1.
nov 27 21:29:30 silverblue systemd[1]: Stopped Login Service.
nov 27 21:29:30 silverblue systemd[1]: Starting Login Service...
nov 27 21:29:30 silverblue systemd[799]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/kmsg: Permission denied
nov 27 21:29:30 silverblue systemd[799]: systemd-logind.service: Failed at step NAMESPACE spawning /sbin/modprobe: Permission denied
nov 27 21:29:30 silverblue systemd[800]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/kmsg: Permission denied
nov 27 21:29:30 silverblue systemd[800]: systemd-logind.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-logind: Permission denied
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
nov 27 21:29:30 silverblue systemd[1]: Failed to start Login Service.
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Service has no hold-off time (RestartSec=0), scheduling restart.
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 2.
nov 27 21:29:30 silverblue systemd[1]: Stopped Login Service.
nov 27 21:29:30 silverblue systemd[1]: Starting Login Service...
nov 27 21:29:30 silverblue systemd[803]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/kmsg: Permission denied
nov 27 21:29:30 silverblue systemd[803]: systemd-logind.service: Failed at step NAMESPACE spawning /sbin/modprobe: Permission denied
nov 27 21:29:30 silverblue systemd[804]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/kmsg: Permission denied
nov 27 21:29:30 silverblue systemd[804]: systemd-logind.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-logind: Permission denied
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
nov 27 21:29:30 silverblue systemd[1]: Failed to start Login Service.
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Service has no hold-off time (RestartSec=0), scheduling restart.
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 3.
nov 27 21:29:30 silverblue systemd[1]: Stopped Login Service.
nov 27 21:29:30 silverblue systemd[1]: Starting Login Service...
nov 27 21:29:30 silverblue systemd[807]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/kmsg: Permission denied
nov 27 21:29:30 silverblue systemd[807]: systemd-logind.service: Failed at step NAMESPACE spawning /sbin/modprobe: Permission denied
nov 27 21:29:30 silverblue systemd[808]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/kmsg: Permission denied
nov 27 21:29:30 silverblue systemd[808]: systemd-logind.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-logind: Permission denied
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
nov 27 21:29:30 silverblue systemd[1]: Failed to start Login Service.
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Service has no hold-off time (RestartSec=0), scheduling restart.
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 4.
nov 27 21:29:30 silverblue systemd[1]: Stopped Login Service.
nov 27 21:29:30 silverblue systemd[1]: Starting Login Service...
nov 27 21:29:30 silverblue systemd[813]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/kmsg: Permission denied
nov 27 21:29:30 silverblue systemd[813]: systemd-logind.service: Failed at step NAMESPACE spawning /sbin/modprobe: Permission denied
nov 27 21:29:30 silverblue systemd[816]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/kmsg: Permission denied
nov 27 21:29:30 silverblue systemd[816]: systemd-logind.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-logind: Permission denied
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
nov 27 21:29:30 silverblue systemd[1]: Failed to start Login Service.
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Service has no hold-off time (RestartSec=0), scheduling restart.
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 5.
nov 27 21:29:30 silverblue systemd[1]: Stopped Login Service.
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Start request repeated too quickly.
nov 27 21:29:30 silverblue systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
nov 27 21:29:30 silverblue systemd[1]: Failed to start Login Service.

Comment 1 Ben Cotton 2020-02-11 17:43:27 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 2 Zbigniew Jędrzejewski-Szmek 2020-04-01 18:41:33 UTC

I'm pretty sure this is fixed now.

Comment 3 Fedora Program Management 2021-04-29 16:00:26 UTC

This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Note You need to log in before you can comment on or make changes to this bug.