Your message dated Wed, 6 Jan 2021 18:21:28 +0100
with message-id <[email protected]>
and subject line Re: Bug#979417: systemd-resolved --status not prepared for
missing files
has caused the Debian Bug report #979417,
regarding systemd-resolved --status not prepared for missing files
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
979417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979417
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 247.2-4
Severity: minor
File: /usr/bin/systemd-resolve
/usr/bin/systemd-resolve --status expects to always find files that in
fact may not be there and are not errors and should not cause the
program to bomb out early.
# systemctl enable --now systemd-resolved
Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service →
/lib/systemd/system/systemd-resolved.service.
Created symlink
/etc/systemd/system/multi-user.target.wants/systemd-resolved.service →
/lib/systemd/system/systemd-resolved.service.
# /usr/bin/systemd-resolve --status | wc
11 33 481
# systemctl --now disable systemd-resolved
Removed /etc/systemd/system/multi-user.target.wants/systemd-resolved.service.
Removed /etc/systemd/system/dbus-org.freedesktop.resolve1.service.
# /usr/bin/systemd-resolve --status | wc
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.
0 0 0
--- End Message ---
--- Begin Message ---
Hello
Am 06.01.21 um 12:24 schrieb 積丹尼 Dan Jacobson:
/usr/bin/systemd-resolve --status expects to always find files that in
fact may not be there and are not errors and should not cause the
program to bomb out early.
# systemctl enable --now systemd-resolved
Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service →
/lib/systemd/system/systemd-resolved.service.
Created symlink
/etc/systemd/system/multi-user.target.wants/systemd-resolved.service →
/lib/systemd/system/systemd-resolved.service.
# /usr/bin/systemd-resolve --status | wc
11 33 481
# systemctl --now disable systemd-resolved
Removed /etc/systemd/system/multi-user.target.wants/systemd-resolved.service.
Removed /etc/systemd/system/dbus-org.freedesktop.resolve1.service.
# /usr/bin/systemd-resolve --status | wc
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.
0 0 0
Please use resolvectl instead of systemd-resolve. The latter is a compat
symlink which is scheduled to go away.
That aside, what you see is expected behaviour.
resolvectl/systemd-resolve tried to contact systemd-resolved. Since it
is not running it tries to start it via D-Bus activation. Since you
disabled the service and removed the
dbus-org.freedesktop.resolve1.service file, D-Bus activation fails and
this error is propagated back to you.
At this point, resolvectl exits, as it can't operate if systemd-resolved
is not running.
Regards,
Michael
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
