[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
Dan Watkins
1896772 at bugs.launchpad.net
Thu Oct 1 13:41:46 UTC 2020
> How did resolve/netif get owned by root?
I don't believe I've ever touched it before, so I'm not sure. I haven't
rebooted since that last comment, I'll do that at some point today to
check if ownership reverts to root.
If it does, what debugging can I perform to determine what's doing it?
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1896772
Title:
systemd-resolved configures no Current Scopes on start
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Running groovy on the desktop, with the systemd packages that migrated
today(/overnight EDT).
# Steps to reproduce:
1) `systemctl restart systemd-resolved.service`
(This is a minimal reproducer, but I first saw this after an apt
upgrade of systemd.)
# Expected behaviour:
DNS continues to work, status looks like this:
Link 2 (enp5s0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.1.1
DNS Servers: 192.168.1.1
DNS Domain: ~.
lan
# Actual behaviour:
DNS is unconfigured:
Link 2 (enp5s0)
Current Scopes: none
DefaultRoute setting: no
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
# Workaround
Disconnecting and reconnecting my network connection restored DNS
functionality.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: systemd 246.5-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: i3
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Wed Sep 23 09:05:42 2020
InstallationDate: Installed on 2019-05-07 (504 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
RebootRequiredPkgs: gnome-shell
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /lib/systemd/system/user at .service → /lib/systemd/system/user at .service.d/timeout.conf
2 overridden configuration files found.
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
------
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: Upgraded to groovy on 2020-06-22 (92 days ago)
dmi.bios.date: 01/25/2019
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: Default string
dmi.board.name: B450M DS3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B450M DS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions
More information about the foundations-bugs
mailing list