systemd-resolved of systemd 239 is failing in cosmic containers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Critical
|
Unassigned |
Bug Description
Hi,
a few hours ago I realized that some of my containers have no working dns resolution anymore.
Usually I'd think I broke something in my host network, but I was suspicious s it hit me on my laptop and on a server at about the same time.
After a while I found that in those containers I have:
systemd-resolve --status
Failed to get global data: Failed to activate service 'org.freedeskto
Later I found two more things leading me to some assumptions:
1. I had no resolv.conf so the service seems to have issues
root@c:~# ll /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Aug 28 22:18 /etc/resolv.conf -> ../run/
root@c:~# ll /run/systemd/
ls: cannot access '/run/systemd/
2. I realized this only affects cosmic container
Bionic container on the same machine is ok (so Host network should be ok I think).
I didn't realize at first as other cosmic's were ok, but those were the containers not updated yet and tonight there was a publish of https:/
Knowing that I checked logs and found:
Aug 29 10:23:25 c systemd[158]: systemd-
Aug 29 10:23:25 c systemd[158]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
Aug 29 10:23:25 c systemd[1]: Dependency failed for Wait for Network to be Configured.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Starting Network Service...
Aug 29 10:23:25 c systemd[161]: systemd-
Aug 29 10:23:25 c systemd[1]: cloud-init.service: Failed to reset devices.list: Operation not permitted
Aug 29 10:23:25 c systemd[161]: systemd-
Aug 29 10:23:25 c systemd[1]: Starting Initial cloud-init job (metadata service crawler)...
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[165]: systemd-
Aug 29 10:23:25 c systemd[1]: Starting Network Service...
Aug 29 10:23:25 c systemd[165]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Starting Network Service...
Aug 29 10:23:25 c systemd[168]: systemd-
Aug 29 10:23:25 c systemd[168]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Starting Network Service...
Aug 29 10:23:25 c systemd[171]: systemd-
Aug 29 10:23:25 c systemd[171]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Failed to set devices.allow on /system.
Aug 29 10:23:25 c systemd[1]: Failed to set devices.allow on /system.
Aug 29 10:23:25 c systemd[1]: Starting Network Name Resolution...
Aug 29 10:23:25 c systemd[174]: systemd-
Aug 29 10:23:25 c systemd[174]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Failed to start Network Name Resolution.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Stopped Network Name Resolution.
Aug 29 10:23:25 c systemd[1]: Failed to set devices.allow on /system.
Aug 29 10:23:25 c systemd[1]: Failed to set devices.allow on /system.
Aug 29 10:23:25 c systemd[1]: Starting Network Name Resolution...
Aug 29 10:23:25 c systemd[183]: systemd-
Aug 29 10:23:25 c systemd[183]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Failed to start Network Name Resolution.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Stopped Network Name Resolution.
Aug 29 10:23:25 c systemd[1]: Failed to set devices.allow on /system.
Aug 29 10:23:25 c systemd[1]: Failed to set devices.allow on /system.
Aug 29 10:23:25 c systemd[1]: Starting Network Name Resolution...
Aug 29 10:23:25 c systemd[186]: systemd-
Aug 29 10:23:25 c systemd[186]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Failed to start Network Name Resolution.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Stopped Network Name Resolution.
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: systemd-
Aug 29 10:23:25 c systemd[1]: Failed to start Network Name Resolution.
Aug 29 10:23:25 c systemd[1]: Reached target Host and Network Name Lookups.
Aug 29 10:23:25 c systemd[1]: Reached target Network.
# systemctl status systemd-resolved
● systemd-
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Wed 2018-08-29 10:39:04 UTC; 10min ago
Docs: man:systemd-
https:/
https:/
https:/
Process: 328 ExecStart=
Main PID: 328 (code=exited, status=217/USER)
Aug 29 10:39:04 c systemd[1]: systemd-
Aug 29 10:39:04 c systemd[1]: systemd-
Aug 29 10:39:04 c systemd[1]: Stopped Network Name Resolution.
Aug 29 10:39:04 c systemd[1]: systemd-
Aug 29 10:39:04 c systemd[1]: systemd-
Aug 29 10:39:04 c systemd[1]: Failed to start Network Name Resolution.
- Dropped my special KVM-LXD profile that I usually use
- Spawned a new Bionic container
# working
- upgraded to systemd of cosmic
Right on upgrade I get the breakage: archive. ubuntu. com/ubuntu cosmic/main amd64 libnss-systemd amd64 239-7ubuntu4 [111 kB] archive. ubuntu. com/ubuntu cosmic/main amd64 libpam-systemd amd64 239-7ubuntu4 [114 kB] archive. ubuntu. com/ubuntu cosmic/main amd64 systemd amd64 239-7ubuntu4 [2967 kB] archive. ubuntu. com/ubuntu cosmic/main amd64 libsystemd0 amd64 239-7ubuntu4 [214 kB] systemd_ 239-7ubuntu4_ amd64.deb ... systemd: amd64 (239-7ubuntu4) over (237-3ubuntu10.3) ... systemd_ 239-7ubuntu4_ amd64.deb ... systemd: amd64 (239-7ubuntu4) over (237-3ubuntu10.3) ... 239-7ubuntu4_ amd64.deb ... _239-7ubuntu4_ amd64.deb ... journald. conf ... logind. conf ... resolved. conf ... system. conf ... networkd. service changed on disk. Run 'systemctl daemon-reload' to reload units. networkd. service, but it can still be activated by: networkd. socket resolved. service changed on disk. Run 'systemctl daemon-reload' to reload units. resolved. service failed because the control process exited with error code. resolved. service" and "journalctl -xe" for details. systemd: amd64: systemd: amd64 depends on systemd (= 239-7ubuntu4); however:
The following packages will be upgraded:
libnss-systemd libpam-systemd libsystemd0 systemd
4 upgraded, 0 newly installed, 0 to remove and 307 not upgraded.
Need to get 3404 kB of archives.
After this operation, 470 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://
Get:2 http://
Get:3 http://
Get:4 http://
Fetched 3404 kB in 1s (4342 kB/s)
(Reading database ... 28491 files and directories currently installed.)
Preparing to unpack .../libnss-
Unpacking libnss-
Preparing to unpack .../libpam-
Unpacking libpam-
Preparing to unpack .../systemd_
Unpacking systemd (239-7ubuntu4) over (237-3ubuntu10.3) ...
Preparing to unpack .../libsystemd0
Unpacking libsystemd0:amd64 (239-7ubuntu4) over (237-3ubuntu10.3) ...
Setting up libsystemd0:amd64 (239-7ubuntu4) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Setting up systemd (239-7ubuntu4) ...
Installing new version of config file /etc/systemd/
Installing new version of config file /etc/systemd/
Installing new version of config file /etc/systemd/
Installing new version of config file /etc/systemd/
Warning: The unit file, source configuration file or drop-ins of systemd-
Warning: Stopping systemd-
systemd-
Warning: The unit file, source configuration file or drop-ins of systemd-
Job for systemd-
See "systemctl status systemd-
dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for dbus (1.12.2-1ubuntu1) ...
dpkg: dependency problems prevent configuration of libnss-
libnss-
Package systemd is not configured yet.
dpkg: error processing package libnss- systemd: amd64 (--configure): systemd: amd64: systemd: amd64 depends on systemd (= 239-7...
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpam-
libpam-