Looking at the code ("src/nspawn/nspawn.c" in v232), it appears that the
existence of /usr/lib/systemd/resolv.conf, which exists on the
problematic system, is triggering the problem.
Not sure how that resolv.conf file got there.
$ ls /usr/lib/systemd/
boot systemd-hostnamed systemd-shutdown
catalog systemd-import systemd-sleep
import-pubring.gpg systemd-importd systemd-socket-proxyd
libsystemd-shared-232.so systemd-initctl systemd-sysctl
network systemd-journald systemd-sysv-install
ntp-units.d systemd-localed systemd-timedated
resolv.conf systemd-logind systemd-timesyncd
system systemd-machined systemd-udevd
systemd systemd-modules-load systemd-update-utmp
systemd-ac-power systemd-networkd systemd-user-sessions
systemd-backlight systemd-networkd-wait-online system-generators
systemd-binfmt systemd-pull system-preset
systemd-cgroups-agent systemd-quotacheck system-shutdown
systemd-cryptsetup systemd-random-seed system-sleep
systemd-export systemd-remount-fs user
systemd-fsck systemd-reply-password user-generators
systemd-fsckd systemd-resolved
systemd-hibernate-resume systemd-rfkill
looks like everything that should be in /lib/systemd and
/usr/lib/systemd is duplicated in both places?! I guess that is most
likely a sysadmin typo, although the system was reloaded relatively
recently and I have no idea how this could have happened.
So I guess this bug could be closed.
Thanks for your help.
Alex
On 11/11/17 11:37, Michael Biebl wrote:
Am 10.11.2017 um 23:05 schrieb Alex King:
$ sudo systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service;
disabled; vendo
Drop-In: /usr/lib/systemd/system/systemd-resolved.service.d
└─resolvconf.conf
Hm, where is this file coming from? It's certainly not from systemd. It
doesn't seem to be coming from Debian either (at least apt-file search
/usr/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf does
not yield any results).
Do you have any custom packages/software in that VPS which might interfere?
Michael
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
