Unit dbus-org.freedesktop.resolve1.service not found.

English Applications
#1 
linux dbus-daemon[981]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
linux dbus-daemon[981]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.2' (uid=0 pid=1047 comm="/usr/sbin/NetworkManager --no-daemon ")
...

Looking at the comments https://bugs.archlinux.org/task/54796
it seems like the problem is either a missing symlink in /etc/systemd/system
or the fact that systemd-resolved.service is disabled.
Although, I’m not sure if this is a bug introduced by a systemd change, or if this setup is intentional by the Tumbleweed devs, or if it’s a product of my custom install.

systemd-resolved is a system service that provides network name resolution to local applications. It implements a caching and validating DNS/DNSSEC stub resolver, as well as an LLMNR and MulticastDNS resolver and responder.

https://www.freedesktop.org/software/systemd/man/systemd-resolved.service.html

Reading that, I’m not really understanding what systemd is trying to accomplish.
What exactly does “network name resolution” refer to regarding “local applications”?
What would I expect to be the symptoms of that not working?

#2

Is this coming from your starting Network Manager? Which log?

The service name is incorrect, the service with the correct name is running fine on my system…

# systemctl status systemd-resolved.service ● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2019-05-05 02:54:36 PDT; 6min ago
     Docs: man:systemd-resolved.service(8)
           https://www.freedesktop.org/wiki/Software/systemd/resolved
           https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
 Main PID: 1171 (systemd-resolve)
   Status: "Processing requests..."
    Tasks: 1 (limit: 2328)
   Memory: 1.9M
   CGroup: /system.slice/systemd-resolved.service
           └─1171 /usr/lib/systemd/systemd-resolved

TSU

#3

What I posted is from journalctl.

I’m not really sure what triggers the message; it keeps appearing – 4 times in one minute most recently.

I did note the difference between the names, but you can see the same in that archlinux bug report.

For some reason systemd-resolved.service is disabled by default on my system:


● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
     Docs: man:systemd-resolved.service(8)
           https://www.freedesktop.org/wiki/Software/systemd/resolved
           https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients

Tumbleweed 20190425
systemd 241

#4

I forgot to mention that I did start the service and it does eliminate the messages.
I’m just not understanding why it was disabled, and what exactly it’s needed for,
since I haven’t noticed any problems other than those messages.

#5

I am in the exact same position as you, and could also observe that in Tumbleweed 20190521 and systemd 242.
As I haven’t noticed any problem yet, I’m more curious than anything, but it would be interesting to find out why.

#6

I think I get even more messages with it enabled.

DNSSEC validation failed for question conncheck.opensuse.org IN A: failed-auxiliary
DNSSEC validation failed for question conncheck.opensuse.org IN AAAA: failed-auxiliary
DNSSEC validation failed for question opensuse.org IN SOA: failed-auxiliary
DNSSEC validation failed for question opensuse.org IN DS: failed-auxiliary
Using degraded feature set (UDP+EDNS0+DO) for DNS server ...]
Using degraded feature set (UDP+EDNS0+DO) for DNS server ...]
Grace period over, resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server ...]
Server ...] does not support DNSSEC, downgrading to non-DNSSEC mode.
Using degraded feature set (UDP+EDNS0) for DNS server ...]
DNSSEC validation failed for question conncheck.opensuse.org IN AAAA: failed-auxiliary
DNSSEC validation failed for question conncheck.opensuse.org IN A: failed-auxiliary
DNSSEC validation failed for question opensuse.org IN SOA: failed-auxiliary
DNSSEC validation failed for question opensuse.org IN DS: failed-auxiliary
Using degraded feature set (TLS+EDNS0) for DNS server ...]
#7

I think you shouldn’t enable systemd-resolved. By default openSUSE uses nscd.

Here’s a workaround, that tells NetworkManager not to use systemd-resolved: https://wiki.archlinux.org/index.php/NetworkManager#Unit_dbus-org.freedesktop.resolve1.service_not_found

#8

There’s a bug report for this: https://bugzilla.opensuse.org/show_bug.cgi?id=1140121

#9

Believe in this case DNSSEC is improperly configured or pointing to a server that doesn’t support.

TSU

#10

With systemd services and Unit configurations,
“Disabled” only means it’s not set to start up automatically on boot but can be started later by any person or process.
It does not mean that the service or application is meant to be more or less permanently non-functional.

If you’re getting error messages,
Then you should try to identify what is invoking this resolver service and then decide whether the service should be “enabled” so it’s available always or should be left to be started up when needed.

TSU

#11

Thanks y’all.