View Issue Details

IDProjectCategoryView StatusLast Update
0016988CentOS-8systemdpublic2020-01-31 10:26
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

There are no notes attached to this issue.

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