Some weird DNS problem?

BebeMischa · March 9, 2022, 5:35pm

Today, out of nothing, I got a weird issue.

Supervisor says installation unsupported. Until yesterday it was not a problem.

core-2022.3.3
supervisor-2022.03.2
debian bullseye full up to date
x86 - 64bit
connected by NabuCasa

supervisor log:

22-03-09 17:23:54 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.systemd1
22-03-09 17:23:54 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.login1
22-03-09 17:23:54 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.hostname1
22-03-09 17:23:54 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.timedate1
22-03-09 17:23:55 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.NetworkManager
22-03-09 17:23:55 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface de.pengutronix.rauc
22-03-09 17:23:55 WARNING (MainThread) [supervisor.dbus.manager] Can't load dbus interface de.pengutronix.rauc: The name de.pengutronix.rauc was not provided by any .service files
22-03-09 17:23:55 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.resolve1
22-03-09 17:23:55 WARNING (MainThread) [supervisor.dbus.manager] Can't load dbus interface org.freedesktop.resolve1: Unit dbus-org.freedesktop.resolve1.service not found.
22-03-09 17:23:55 INFO (MainThread) [supervisor.host.info] Updating local host information
22-03-09 18:23:55 INFO (MainThread) [supervisor.host.services] Updating service information
22-03-09 18:23:55 INFO (MainThread) [supervisor.host.network] Updating local network information
22-03-09 18:23:55 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
22-03-09 18:23:55 INFO (MainThread) [supervisor.host.manager] Host information reload completed
22-03-09 18:23:55 INFO (MainThread) [supervisor.host.apparmor] Loading AppArmor Profiles: {'hassio-supervisor'}
22-03-09 18:23:55 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-cli with version 2021.12.0
22-03-09 18:23:55 INFO (MainThread) [supervisor.plugins.cli] Starting CLI plugin
22-03-09 18:23:56 INFO (SyncWorker_1) [supervisor.docker.cli] Starting CLI ghcr.io/home-assistant/amd64-hassio-cli with version 2021.12.0 - 172.30.32.5
22-03-09 18:23:56 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-dns with version 2021.06.0
22-03-09 18:23:56 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
22-03-09 18:23:57 INFO (SyncWorker_0) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/amd64-hassio-dns with version 2021.06.0 - 172.30.32.3
22-03-09 18:23:57 INFO (MainThread) [supervisor.plugins.dns] Updated /etc/resolv.conf
22-03-09 18:23:57 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-audio with version 2021.07.0
22-03-09 18:23:57 INFO (MainThread) [supervisor.plugins.audio] Starting Audio plugin
22-03-09 18:23:58 INFO (SyncWorker_1) [supervisor.docker.audio] Starting Audio ghcr.io/home-assistant/amd64-hassio-audio with version 2021.07.0 - 172.30.32.4
22-03-09 18:23:58 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-observer with version 2021.10.0
22-03-09 18:23:58 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-multicast with version 2022.02.0
22-03-09 18:23:58 INFO (MainThread) [supervisor.plugins.multicast] Starting Multicast plugin
22-03-09 18:23:59 INFO (SyncWorker_1) [supervisor.docker.multicast] Starting Multicast ghcr.io/home-assistant/amd64-hassio-multicast with version 2022.02.0 - Host
22-03-09 18:23:59 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
22-03-09 18:24:19 WARNING (MainThread) [supervisor.utils.codenotary] rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 34.207.232.93:443: i/o timeout"
22-03-09 18:24:19 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 1 Home Assistant secrets
22-03-09 18:24:19 INFO (SyncWorker_3) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/qemux86-64-homeassistant with version 2022.3.3
22-03-09 18:24:19 INFO (MainThread) [supervisor.os.manager] No Home Assistant Operating System found
22-03-09 18:24:20 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/core repository
22-03-09 18:24:20 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/f5a8083e repository
22-03-09 18:24:20 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/a0d7b954 repository
22-03-09 18:24:20 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/6872d8d8 repository
22-03-09 18:24:21 INFO (MainThread) [supervisor.store] Loading add-ons from store: 65 all - 65 new - 0 remove
22-03-09 18:24:21 INFO (MainThread) [supervisor.addons] Found 9 installed add-ons
22-03-09 18:24:21 INFO (SyncWorker_5) [supervisor.docker.interface] Attaching to homeassistant/amd64-addon-configurator with version 5.3.3
22-03-09 18:24:21 INFO (SyncWorker_4) [supervisor.docker.interface] Attaching to homeassistant/amd64-addon-mariadb with version 2.4.0
22-03-09 18:24:21 INFO (SyncWorker_3) [supervisor.docker.interface] Attaching to homeassistant/amd64-addon-vlc with version 0.1.3
22-03-09 18:24:21 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/hassio-addons/vscode/amd64 with version 4.1.0
22-03-09 18:24:21 INFO (SyncWorker_6) [supervisor.docker.interface] Attaching to homeassistant/amd64-addon-ssh with version 9.3.0
22-03-09 18:24:21 INFO (SyncWorker_7) [supervisor.docker.interface] Attaching to homeassistant/amd64-addon-mosquitto with version 6.0.1
22-03-09 18:24:21 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/amd64-addon-samba with version 9.5.1
22-03-09 18:24:21 INFO (SyncWorker_2) [supervisor.docker.interface] Attaching to f5a8083e/amd64-addon-dutch_gas_prices with version 2022.2.27.1
22-03-09 18:24:21 INFO (SyncWorker_5) [supervisor.docker.interface] Attaching to homeassistant/amd64-addon-zwave_js with version 0.1.54
22-03-09 18:24:21 INFO (MainThread) [supervisor.backups.manager] Found 13 backup files
22-03-09 18:24:21 INFO (MainThread) [supervisor.discovery] Loaded 3 messages
22-03-09 18:24:21 INFO (MainThread) [supervisor.ingress] Loaded 0 ingress sessions
22-03-09 18:24:21 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.SETUP
22-03-09 18:24:21 INFO (MainThread) [supervisor.resolution.check] System checks complete
22-03-09 18:24:21 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
22-03-09 18:24:21 WARNING (MainThread) [supervisor.resolution.evaluations.base] Systemd-Resolved is required for DNS in Home Assistant. (more-info: https://www.home-assistant.io/more-info/unsupported/systemd_resolved)
22-03-09 18:24:21 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-03-09 18:24:21 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not running - CoreState.SETUP
22-03-09 18:24:21 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
22-03-09 18:24:21 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-03-09 18:24:21 INFO (MainThread) [__main__] Running Supervisor
22-03-09 18:24:21 WARNING (MainThread) [supervisor.core] System running in a unsupported environment!
22-03-09 18:24:21 INFO (MainThread) [supervisor.jobs] 'OSManager.mark_healthy' blocked from execution, no Home Assistant OS available
22-03-09 18:24:21 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' starting 0 add-ons
22-03-09 18:24:22 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SYSTEM' starting 2 add-ons
22-03-09 18:24:23 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-mosquitto with version 6.0.1
22-03-09 18:24:24 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-mariadb with version 2.4.0
22-03-09 18:24:26 INFO (MainThread) [supervisor.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
22-03-09 18:24:28 INFO (MainThread) [supervisor.services.modules.mysql] Set core_mariadb as service provider for MySQL
22-03-09 18:24:29 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SERVICES' starting 6 add-ons
22-03-09 18:24:30 INFO (SyncWorker_6) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-zwave_js with version 0.1.54
22-03-09 18:24:30 INFO (SyncWorker_4) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-ssh with version 9.3.0
22-03-09 18:24:31 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-samba with version 9.5.1
22-03-09 18:24:32 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-vlc with version 0.1.3
22-03-09 18:24:32 INFO (MainThread) [supervisor.api.middleware.security] /network/interface/default/info access from core_samba
22-03-09 18:24:33 INFO (MainThread) [supervisor.api.middleware.security] /host/info access from core_zwave_js
22-03-09 18:24:33 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/vscode/amd64 with version 4.1.0
22-03-09 18:24:33 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mosquitto'
22-03-09 18:24:33 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache
22-03-09 18:24:34 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on f5a8083e/amd64-addon-dutch_gas_prices with version 2022.2.27.1
22-03-09 18:24:39 INFO (MainThread) [supervisor.core] Start Home Assistant Core
22-03-09 18:24:39 INFO (SyncWorker_2) [supervisor.docker.interface] Starting homeassistant
22-03-09 18:24:40 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
22-03-09 18:24:54 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.STARTUP
22-03-09 18:24:54 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-03-09 18:24:56 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
22-03-09 18:26:06 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
22-03-09 18:26:06 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.APPLICATION' starting 1 add-ons
22-03-09 18:26:07 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-configurator with version 5.3.3
22-03-09 18:26:12 INFO (MainThread) [supervisor.misc.tasks] All core tasks are scheduled
22-03-09 18:26:12 INFO (MainThread) [supervisor.core] Supervisor is up and running
22-03-09 18:26:12 INFO (MainThread) [supervisor.host.info] Updating local host information
22-03-09 18:26:12 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
22-03-09 18:26:12 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
22-03-09 18:26:12 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
22-03-09 18:26:12 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.PLUGIN
22-03-09 18:26:12 INFO (MainThread) [supervisor.host.services] Updating service information
22-03-09 18:26:13 INFO (MainThread) [supervisor.host.network] Updating local network information
22-03-09 18:26:13 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
22-03-09 18:26:13 INFO (MainThread) [supervisor.host.manager] Host information reload completed

This is suspicious, if I’m not wrong, that IP is of GitHub:

22-03-09 18:24:19 WARNING (MainThread) [supervisor.utils.codenotary] rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 34.207.232.93:443: i/o timeout"

Anyone can give me a push in the right direction?

Thanks in advance

typeonegative · March 9, 2022, 7:12pm

i have same issue

hassfo · March 9, 2022, 7:22pm

Hi BebeMischa,
I had similar issues today.
I found that the HA update process requires access to cas.codenotary.com.
My DNS resolver returned same IP 34.207.232.93 as in your log.
Browsing to cas.codenotary.com on my PC timed out, but with a mobile device it worked via mobile network, so I assumed I have an issue with DNS in my home network.

Since I am using pi-hole as DNS resolver & filter I cleared its cache.
Next time I got a different IP for cas.codenotary.com: 35.168.17.115.
After that the update of HA core succeeded.
Maybe this helps?

Greetings
Nob

BebeMischa · March 9, 2022, 7:32pm

Thank you, Nob

Well, I kind of understand, what you are saying. I’m not very familiar with DNS.
I think, my resolver is the internet modem.
I have restarted the modem. Did not help.
I have no any issues with other things, only HA.

Steps I’ve tried until now:
Restart HA alone - no result
Restart the HA server - no result
Apt update, upgrade and full-upgrade on the server - no result
Rerun the HA supervised install script - no result

I saw the IP with 115 on the end that you mention also passing by, but with same error. That IP is registered by Amazon? Weird…

I guess, when I’ve restarted the modem, it’s cache got cleared, so that has to be ok?

hassfo · March 9, 2022, 7:44pm

Hello again,

Yes, I would expect, that resetting your internet router will clear the DNS cache.

In the meantime I found that the adress …115 seem to have problems sometimes:

22-03-09 20:27:16 WARNING (MainThread) [supervisor.utils.codenotary] rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 35.168.17.115:443: i/o timeout"

Maybe there is a more general problem with the server or the network.
I saw that frenck filed a bug report:
https://github.com/codenotary/cas/issues/263

br, Nob

hassfo · March 9, 2022, 7:48pm

Just found this explanation:
https://github.com/home-assistant/supervisor/issues/3495#issuecomment-1063246444
This confirms some trouble and the DNS change.
Maybe you just try it again later…

Nob

BebeMischa · March 9, 2022, 7:48pm

Thank you, I will follow it there, I was almost sure, the problem is not on my side. All steps I have made are anyway part of usual maintenance (except rerun of install, but that does not kill anything ).
My install always has been healthy. So I already suspected some service outside to be faulty.

Well, your invested time is appreciated

hassfo · March 9, 2022, 7:50pm

You are welcome!
I felt the same, since I use to keep my installation nice and clean

BebeMischa · March 9, 2022, 8:25pm

Finally, this saved my day:

sudo systemd-resolve --flush-caches
sudo /etc/init.d/networking restart

kaven · March 10, 2022, 1:15am

For some reason, I had to run this on my system:

sudo systemctl enable systemd-resolved.service

Everything was working until today when I noticed the superviser was flagged as unsupported. I’m not sure what caused the issue.

gromero · March 10, 2022, 6:53am

Can this:

Or this:

Be run via “SSH & Web Terminal” in the GUI, or does it need to be done on the CLI of the device itself?
I’m running the OS on a NUK, but it’s a PITA to hook up a screen/keyboard each time.

I’m still getting the same issue, have already tried restarting my Pihole (DNS server).

kaven · March 10, 2022, 2:23pm

You can do it over SSH. I’m not sure if you can do it within home assistant itself as it’s running in a docker container.

On a side note, I still can’t update because I’m now getting a script error during the update.

BebeMischa · March 10, 2022, 3:29pm

New supervisor update is released. All my problems seems gone.

k8gg · March 10, 2022, 4:31pm

Per the issue line of post #5 above, the problem is with the code signing server, and it is still open, it seems.

So the Supervisor 2022.03.3 (& .2 earlier) update today includes this:

#3504 Disable CAS until it work

Richdem · March 10, 2022, 7:23pm

Did this fix the issue?

I have just finished setting up a newer machine for Home Assistant and I noticed my supervisor was not supported. I then went and checked my main machine and it was the same. I also had no issues prior to this. I am running the latest Debian 11 on both machines (I used the tutorial on these forums for the install of Debian, Supervisor & Home Assistant)

Is there anything else that needs to be done? I would like to get this straightened out before switching machines

Regards

Richard

kaven · March 10, 2022, 11:22pm

The update to supervisor-2022.03.3 fixed my issue. It was auto installed earlier.

Richdem · March 11, 2022, 4:16pm

I am running the same version if supervisor and I still have the issue,

When you run the following

sudo systemctl enable systemd-resolved.service

Is there anything else that needs to be done?

BebeMischa · March 11, 2022, 7:01pm

sudo systemctl enable systemd-resolved.service
sudo systemd-resolve --flush-caches
sudo /etc/init.d/networking restart
sudo reboot

that did the trick and can not do any harm

Richdem · March 11, 2022, 7:26pm

Thank you I will give that a try on my test machine

Richdem · March 11, 2022, 7:44pm

Are you seeing the following error in your log?

22-03-11 14:32:49 WARNING (MainThread) [supervisor.dbus.manager] Can’t load dbus interface de.pengutronix.rauc: The name de.pengutronix.rauc was not provided by any .service files

This was after I ran the above commands and restarted Home Assistant. Not sure if this is a big issue but now Supervisor is showing as official