search

home-assistant / operating-system

:beginner: Home Assistant Operating System
Apache License 2.0
5.03k stars 986 forks source link

host_internet: false - after OS 6.1 installed #1467

Closed Masterz69 closed 2 years ago

Masterz69 commented 3 years ago

Hardware Environment

Home Assistant OS release:

Masterz69 commented 3 years ago

Forgot to add. Yesterday after host restart - all was fine, Supervisor was able to update add-ons. But today again it fails. Highly likely, because of host_internet: false.

Masterz69 commented 3 years ago 
➜  ~ arp -n | sort -k 1
172.17.0.2               ether   02:42:ac:11:00:02   C                     docker0
172.30.32.2              ether   02:42:ac:1e:20:02   C                     hassio
172.30.32.3              ether   02:42:ac:1e:20:03   C                     hassio
172.30.32.6              ether   02:42:ac:1e:20:06   C                     hassio
172.30.33.0              ether   02:42:ac:1e:21:00   C                     hassio
172.30.33.1              ether   02:42:ac:1e:21:01   C                     hassio
172.30.33.2              ether   02:42:ac:1e:21:02   C                     hassio
172.30.33.3              ether   02:42:ac:1e:21:03   C                     hassio
192.168.1.1              ether   74:d2:1d:be:66:53   C                     eth0
192.168.1.1              ether   74:d2:1d:be:66:53   C                     wlan0
agners commented 3 years ago

Hm, it seems the Supervisor cannot talk to the Host OS through D-Bus for some reason:

21-07-16 17:29:45 WARNING (MainThread) [supervisor.host.network] Can't update connectivity information: Error: Timeout was reached

Do you see any negative impact due to this?

agners commented 3 years ago

This might be related to #1483.

vmartinv commented 3 years ago

Hello I'm experiencing the same problem after updating OS from 6.1 to 6.2.

supervisor logs

21-08-05 11:08:46 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/ssh/aarch64 with version 9.0.0
21-08-05 11:08:50 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64499 ssl:default [Connect call failed ('172.30.32.1', 64499)]
21-08-05 11:09:00 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from a0d7b954_ssh
21-08-05 11:09:00 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from a0d7b954_ssh
21-08-05 11:09:00 INFO (MainThread) [supervisor.api.middleware.security] /host/info access from a0d7b954_ssh
21-08-05 11:09:00 INFO (MainThread) [supervisor.api.middleware.security] /core/info access from a0d7b954_ssh
21-08-05 11:09:06 WARNING (MainThread) [supervisor.host.network] Can't update connectivity information: Error: Timeout was reached
21-08-05 11:09:11 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from a0d7b954_ssh
21-08-05 11:09:46 WARNING (MainThread) [supervisor.host.network] Can't update connectivity information: Error: Timeout was reached
21-08-05 11:11:01 WARNING (MainThread) [supervisor.host.network] Can't update connectivity information: Error: Timeout was reached
21-08-05 11:11:42 WARNING (MainThread) [supervisor.host.network] Can't update connectivity information: Error: Timeout was reached
21-08-05 11:12:04 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from a0d7b954_ssh
21-08-05 11:12:04 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from a0d7b954_ssh
21-08-05 11:12:04 INFO (MainThread) [supervisor.api.middleware.security] /host/info access from a0d7b954_ssh
21-08-05 11:12:04 INFO (MainThread) [supervisor.api.middleware.security] /core/info access from a0d7b954_ssh
21-08-05 11:12:17 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from a0d7b954_ssh
21-08-05 11:12:22 WARNING (MainThread) [supervisor.host.network] Can't update connectivity information: Error: Timeout was reached
21-08-05 11:13:02 WARNING (MainThread) [supervisor.host.network] Can't update connectivity information: Error: Timeout was reached
21-08-05 11:13:04 WARNING (MainThread) [supervisor.jobs] 'HomeAssistantCore.update' blocked from execution, no host internet connection
21-08-05 11:13:57 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-08-05 11:14:53 WARNING (MainThread) [supervisor.host.network] Can't update connectivity information: Error: Timeout was reached
21-08-05 11:15:00 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret google_drive_backup_password
21-08-05 11:15:33 WARNING (MainThread) [supervisor.host.network] Can't update connectivity information: Error: Timeout was reached
21-08-05 11:16:48 WARNING (MainThread) [supervisor.host.network] Can't update connectivity information: Error: Timeout was reached
21-08-05 11:17:08 WARNING (MainThread) [supervisor.jobs] 'HomeAssistantCore.update' blocked from execution, no host internet connection

core logs

2021-08-05 11:13:04 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /core/update - 'HomeAssistantCore.update' blocked from execution, no host internet connection

system info

➜  ~ ha network info                                  
docker:
  address: 172.30.32.0/23
  dns: 172.30.32.3
  gateway: 172.30.32.1
  interface: hassio
host_internet: false
interfaces:
- connected: true
  enabled: true
  interface: eth0
  ipv4:
    address:
    - 192.168.0.97/24
    gateway: 192.168.0.1
    method: static
    nameservers:
    - 192.168.0.1
  ipv6:
    address:
    - fe80::87f3:f7f6:b1f1:4caa/64
    gateway: null
    method: auto
    nameservers: []
  primary: true
  type: ethernet
  vlan: null
  wifi: null
- connected: false
  enabled: false
  interface: wlan0
  ipv4:
    address: []
    gateway: null
    method: disabled
    nameservers: []
  ipv6:
    address: []
    gateway: null
    method: disabled
    nameservers: []
  primary: false
  type: wireless
  vlan: null
  wifi: null
supervisor_internet: true
➜  ~ ha info        
arch: aarch64
channel: stable
docker: 20.10.6
features:
- reboot
- shutdown
- services
- network
- hostname
- timedate
- hassos
hassos: "6.2"
homeassistant: 2021.7.3
hostname: homeassistant
logging: info
machine: raspberrypi4-64
operating_system: Home Assistant OS 6.2
state: running
supervisor: 2021.06.8
supported: true
supported_arch:
- aarch64
- armv7
- armhf
timezone: Europe/London
➜  ~ ping www.hp.com
PING www.hp.com (23.55.59.11): 56 data bytes
64 bytes from 23.55.59.11: seq=0 ttl=57 time=20.365 ms
64 bytes from 23.55.59.11: seq=1 ttl=57 time=26.016 ms
64 bytes from 23.55.59.11: seq=2 ttl=57 time=16.085 ms
64 bytes from 23.55.59.11: seq=3 ttl=57 time=16.070 ms
➜  ~ curl https://version.home-assistant.io/online.txt
NetworkManager is online
TasyDevilsky commented 3 years ago

I've got this problem too.

agners commented 3 years ago

Can you login using SSH to the underlying OS using this guide.

From there, check the following things:

curl https://version.home-assistant.io/online.txt
resolvectl query version.home-assistant.io
resolvectl status
TasyDevilsky commented 3 years ago

Can you login using SSH to the underlying OS using this guide.

From there, check the following things:

curl https://version.home-assistant.io/online.txt
resolvectl query version.home-assistant.io
resolvectl status

Hmm, It's pretty weird. 

# curl https://version.home-assistant.io/online.txt
NetworkManager is online
# resolvectl query version.home-assistant.io
version.home-assistant.io: 2606:4700:20::ac43:445a -- link: eth0
                           2606:4700:20::681a:5ee -- link: eth0
                           2606:4700:20::681a:4ee -- link: eth0
                           172.67.68.90        -- link: eth0
                           104.26.5.238        -- link: eth0
                           104.26.4.238        -- link: eth0

-- Information acquired via protocol DNS in 4.1ms.
-- Data is authenticated: no
# resolvectl status
Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported      
    resolv.conf mode: foreign                                             
  Current DNS Server: 192.168.0.1                                         
         DNS Servers: 192.168.0.1                                         
Fallback DNS Servers: 1.1.1.1 8.8.8.8 1.0.0.1 8.8.4.4 2606:4700:4700::1111
                      2001:4860:4860::8888 2606:4700:4700::1001           
                      2001:4860:4860::8844                                

Link 2 (dummy0)
Current Scopes: none                                                        
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 3 (eth0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6               
         Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.0.1                                                 
       DNS Servers: 192.168.0.1                                                 
        DNS Domain: ~.                                                          

Link 4 (wlan0)
Current Scopes: none                                                        
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 5 (hassio)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6                                       
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 6 (docker0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6                                       
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 8 (veth6a3dd77)
Current Scopes: LLMNR/IPv6                                                  
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 10 (vethf790af7)
Current Scopes: LLMNR/IPv6                                                  
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 12 (veth6c57bf4)
Current Scopes: LLMNR/IPv6                                                  
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 14 (vetha405030)
Current Scopes: LLMNR/IPv6                                                  
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 16 (veth2b24bdd)
Current Scopes: LLMNR/IPv6                                                  
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 18 (vethd710750)
Current Scopes: LLMNR/IPv6                                                  
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 20 (vethc3488c5)
Current Scopes: LLMNR/IPv6                                                  
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 22 (vethdf11a75)
Current Scopes: LLMNR/IPv6                                                  
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 24 (veth7017b9f)
Current Scopes: LLMNR/IPv6                                                  
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 26 (vetheccf563)
Current Scopes: LLMNR/IPv6                                                  
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 28 (vethb3df5a0)
Current Scopes: LLMNR/IPv6                                                  
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 30 (veth6e1a790)
Current Scopes: LLMNR/IPv6                                                  
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
#
vmartinv commented 3 years ago

I was able to solve this... I was using manual mode because I have my own DNS servers running but this appear to have messed up with the OS. I went to Supervisor->System->In the IP address section, pressed the change button->In IPv4 section of my connection I set an external DNS address (Google is 8.8.8.8), the previous one was wrong. It would be good if there were some link to troubleshooting in that error message.

Masterz69 commented 3 years ago

There no such an issue noticed before 2021.6.x versions. Connectivity stays FULL for some time (last time >12 hours), then become LIMITED. IMHO root cause not in external/local DNS servers.

gitarman94 commented 3 years ago

Just reinstalled hassio right off the website using latest of everything and I too am still receiving this error. Previously I was using 6.4 and updated the OS version first, which then prevented me from updating the core. But ever since that update, I can't even download plugins now.

Masterz69 commented 3 years ago

So far in my case - after setting different IP addresses for wlan0 & eth0 - issue appear no more.

agners commented 2 years ago

It seems that the issue in general is not reported often anymore. It seems that the update of systemd (which brings a new version of the DNS resolver systemd-resolved used on the host OS) helped. In any case, thanks for your contributions!

nagosuka commented 1 year ago

I am currently having this issue which started sometime the past week...

nagosuka commented 1 year ago

Nevermind. DNS issue with pi-hole