Unsupported system - Systemd-Resolved issues

Configuration
1

Suddenly I got this error message that "System is unsupported because Systemd Resolved is missing, inactive or misconfigured. "
systemd-resolved is running and there are no problems at all.

● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
     Active: active (running) since Sun 2024-01-28 13:26:01 EET; 12min ago
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
   Main PID: 2209 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 9320)
     Memory: 3.0M
     CGroup: /system.slice/systemd-resolved.service
             └─2209 /lib/systemd/systemd-resolved

Jan 28 13:26:01 orava systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
Jan 28 13:26:01 orava systemd-resolved[2209]: Positive Trust Anchors:
Jan 28 13:26:01 orava systemd-resolved[2209]: . IN DS 20326 8 2 e06d44b80b09bbc683457104237c7f8ec8d
Jan 28 13:26:01 orava systemd-resolved[2209]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.>
Jan 28 13:26:01 orava systemd-resolved[2209]: Using system hostname 'orava'.
Jan 28 13:26:01 orava systemd[1]: Started systemd-resolved.service - Network Name Resolution.

For practical reasons, I have also Tailscale installed in the system. Can it cause this problem?
Does this “unsupported” mean that I cannot update something?
Edit, this is Debian Bookworm supervised,

  • Core 2024.1.5
  • Supervisor 2023.12.1
  • Frontend 20240104.0
2

No. Only “unhealthy” status will prevent you from upgrading.

3

I also get this error and have no idea how to resolve it. I’m not very good with CLI, if indeed that is what is needed to fix my issue that came out of nowhere

4

If I remember right I had to run

sudo docker restart hassio_supervisor

In my Debian supervised. Then it was resolved. This was not documented anywhere.
I hope I remember right.

5

Correct :slight_smile:

1 Like