Bug ID 1162472
Summary systemd in rescue image tries to mount / with MS_SLAVE, but it fails -- logind does not start
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Basesystem
Assignee systemd-maintainers@suse.de
Reporter jslaby@suse.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Start rescue system from Tumbleweed cd and see logind failing:
> # systemctl status systemd-logind.service
> ��� systemd-logind.service - Login Service
>      Loaded: loaded (/mounts/mp_0000/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled)
>     Drop-In: /mounts/mp_0000/usr/lib/systemd/system/systemd-logind.service.d
>              ������nosandbox.conf
>      Active: failed (Result: exit-code) since Mon 2020-02-03 09:25:20 UTC; 4min 48s ago
>        Docs: man:systemd-logind.service(8)
>              man:logind.conf(5)
>              https://www.freedesktop.org/wiki/Software/systemd/logind
>              https://www.freedesktop.org/wiki/Software/systemd/multiseat
>     Process: 2926 ExecStartPre=/sbin/modprobe -abq drm (code=exited, status=226/NAMESPACE)
>     Process: 2927 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=226/NAMESPACE)
>    Main PID: 2927 (code=exited, status=226/NAMESPACE)
>
> Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 5.
> Feb 03 09:25:20 rescue systemd[1]: Stopped Login Service.
> Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Start request repeated too quickly.
> Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
> Feb 03 09:25:20 rescue systemd[1]: Failed to start Login Service.

When you try to log in as root, it needs to timeout first and only then you get
a shell:
> Feb 03 09:25:20 rescue systemd[2927]: systemd-logind.service: Failed to set up mount namespacing: Invalid argument
> Feb 03 09:25:20 rescue systemd[2927]: systemd-logind.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-logind: Invalid argument
> Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE
> Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
> Feb 03 09:25:20 rescue systemd[1]: Failed to start Login Service.
> Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 5.
> Feb 03 09:25:20 rescue systemd[1]: Stopped Login Service.
> Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Start request repeated too quickly.
> Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
> Feb 03 09:25:20 rescue systemd[1]: Failed to start Login Service.
> Feb 03 09:25:45 rescue dbus-daemon[2408]: [system] Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
> Feb 03 09:25:45 rescue login[2835]: pam_systemd(login:session): Failed to create

Leap 15.2 is OK. My first suspect would be:
https://github.com/openSUSE/systemd/commit/9b68367b3a076c168c9f0e8659d0122237a55197

The behaviour of the 15.2 and TW kernels is the same:
# mount --make-rslave /
mount.bin: /: not mount point or bad option.


You are receiving this mail because: