View Issue Details

IDProjectCategoryView StatusLast Update
0016988CentOS-8systemdpublic2020-09-03 00:34
ReporterStufo76 
PrioritynormalSeveritymajorReproducibilityalways
Status newResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0016988: systemd-resolved fails to start at boot
Descriptionsystemd-resolved fails to start at boot.

If I manually start it, all works fine.
Steps To ReproduceEnable systemd-resolved:
sudo systemctl enable --now systemd-resolved
sudo rm -f /etc/resolv.conf
sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

Reboot system

After reboot, systemd-resolved fails to start with status=226/NAMESPACE

If I manually start it, all works fine.
Additional InformationJan 28 21:24:33 localhost systemd[1120]: systemd-resolved.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-resolved: Read-only file system
Jan 28 21:24:33 localhost systemd[1135]: systemd-resolved.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-resolved: Read-only file system
Jan 28 21:24:33 localhost systemd[1139]: systemd-resolved.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-resolved: Read-only file system
Jan 28 21:24:33 localhost systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
Jan 28 21:24:33 localhost systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Jan 28 21:24:33 localhost systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Jan 28 21:24:33 localhost systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 3.
Jan 28 21:24:33 localhost systemd[1140]: systemd-resolved.service: Failed to set up mount namespacing: Read-only file system
Jan 28 21:24:33 localhost systemd[1140]: systemd-resolved.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-resolved: Read-only file system
Jan 28 21:24:33 localhost systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
Jan 28 21:24:33 localhost systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Jan 28 21:24:33 localhost systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Jan 28 21:24:33 localhost systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 4.

NAME="CentOS Linux"
VERSION="8 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Linux 8 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-8"
CENTOS_MANTISBT_PROJECT_VERSION="8"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="8"

4.18.0-147.3.1.el8_1.x86_64
Tags226/NAMESPACE, systemd-resolved

Activities

olifre

olifre

2020-09-02 21:59

reporter   ~0037624

Also experience this, but not each time when rebooting a machine. It seems RedHat has documented this issue and potentially a solution to it:
https://access.redhat.com/solutions/4981731
Sadly, it is paywalled and can not be accessed :-(.
olifre

olifre

2020-09-03 00:34

reporter   ~0037626

After further research and guesswork, I believe that this:
https://github.com/systemd-rhel/rhel-8/pull/68
is the fix, this:
https://bugzilla.redhat.com/show_bug.cgi?id=1810869
is the upstream issue (but I can't access it) and this:
https://git.centos.org/rpms/systemd/blob/36d2f4d36d0afb87c2174089ce36c430b9db8c6d/f/SPECS/systemd.spec#_1194
indicates that systemd-239-32from June should fix it. Latest in CentOS 8 is still 239-31, though.

Issue History

Date Modified Username Field Change
2020-01-30 05:03 Stufo76 New Issue
2020-01-30 05:03 Stufo76 Tag Attached: systemd-resolved
2020-01-30 05:03 Stufo76 Tag Attached: 226/NAMESPACE
2020-09-02 21:59 olifre Note Added: 0037624
2020-09-03 00:34 olifre Note Added: 0037626