krash
May 26, 2020, 8:00am
1
Tried to update hassio this morning, and saw that a Supervisor update is also available.
Tried both but they give an unknown error:
Here are the logs:
20-05-26 07:57:50 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.110.2
20-05-26 07:57:50 INFO (SyncWorker_6) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.109.4 to homeassistant/qemux86-64-homeassistant:0.110.2
20-05-26 07:57:50 INFO (SyncWorker_6) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.110.2.
20-05-26 07:57:50 ERROR (SyncWorker_6) [supervisor.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.110.2 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:52509->[::1]:53: read: connection refused").
20-05-26 07:57:50 WARNING (MainThread) [supervisor.homeassistant] Update Home Assistant image fails
---
20-05-26 07:57:51 INFO (MainThread) [supervisor.supervisor] Update Supervisor to version 224
20-05-26 07:57:51 INFO (SyncWorker_17) [supervisor.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag 224.
20-05-26 07:57:51 ERROR (SyncWorker_17) [supervisor.docker.interface] Can't install homeassistant/amd64-hassio-supervisor:224 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:46901->[::1]:53: read: connection refused").
20-05-26 07:57:51 ERROR (MainThread) [supervisor.supervisor] Update of Supervisor fails!
Btw, First time i update Supervisor, but have updated core successfully before.
Is there something i should look into or should i try later?
1 Like
tom_w
May 26, 2020, 9:38am
2
Same here, unable to update using hass.io supervisor on RPI4
Same error for me. Already tried to update via Supervisor and terminal, both failed with the same cryptic error message.
I also reduced my configuration.yaml to default_config: and some logger settings. No success.
Is there any idea?
Update:
After looking for the correct logs I found:
20-05-26 13:12:14 ERROR (SyncWorker_8) [supervisor.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.110.2 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.110.2: No such image: homeassistant/qemux86-64-homeassistant:0.110.2").
20-05-26 13:12:14 WARNING (MainThread) [supervisor.homeassistant] Update Home Assistant image fails
Any idea or solution?
krash
May 26, 2020, 3:10pm
4
I have a feeling it will be resolved on its own, give it a couple hours.
francisp
May 26, 2020, 3:21pm
5
That is simple to solve: you have insufficient disk space.
krash
May 29, 2020, 7:22am
6
My reported disk usage is at 24%
francisp
May 29, 2020, 7:35am
7
25% does not mean anything. How big is your SD ? You need 2.5 to 3 times the space HA occupies now to upgrade.
krash
May 29, 2020, 7:48am
8
If i’m not mistaken it’s a 128gb ssd.
BTW, i’m getting 500 error, not 404 like our friend above.
20-05-29 07:48:13 ERROR (SyncWorker_2) [supervisor.docker.interface] Can't install homeassistant/amd64-hassio-supervisor:224 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:49716->[::1]:53: read: connection refused").
20-05-29 07:48:13 ERROR (MainThread) [supervisor.supervisor] Update of Supervisor fails!
20-05-29 07:48:22 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.110.3
20-05-29 07:48:22 INFO (SyncWorker_9) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.109.4 to homeassistant/qemux86-64-homeassistant:0.110.3
20-05-29 07:48:22 INFO (SyncWorker_9) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.110.3.
20-05-29 07:48:22 ERROR (SyncWorker_9) [supervisor.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.110.3 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:38646->[::1]:53: read: connection refused").
20-05-29 07:48:22 WARNING (MainThread) [supervisor.homeassistant] Update Home Assistant image fails
Did you try to pull manually the last docker image? I see22 INFO (SyncWorker_9) [supervisor.docker.interface] Pull image22 ERROR (SyncWorker_9) [supervisor.docker.interface] Can’t install
Or try to type docker images and check if in your list there is the last version
tom_w
May 29, 2020, 8:34am
10
It seems we are all having different issues with the same end result.
My issue is now resolved - I had an onvif camera in my configuration, which was unplugged. This caused HA to hang indefinitely on startup, making the supervisor believe the upgrade failed, and it uninstalled and rolled back the docker image. There was no information in the logs, in that failed run or afterwards.
francisp
May 29, 2020, 9:45am
11
SSH in to the host (not the HA container) and issue the command
docker pull homeassistant/qemux86-64-homeassistant:0.110.3
What do you get ?
krash
May 31, 2020, 8:45am
12
Usucessful:
Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:54812->[::1]:53: read: connection refused
My problem seems to be even worst, i can’t download plugins from the addons store:
20-05-31 08:39:18 INFO (MainThread) [supervisor.host.apparmor] Add or Update AppArmor profile: core_dnsmasq
20-05-31 08:39:18 INFO (MainThread) [supervisor.host.services] Reload local service hassio-apparmor.service
20-05-31 08:39:18 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1
20-05-31 08:39:18 INFO (SyncWorker_3) [supervisor.docker.interface] Pull image homeassistant/amd64-addon-dnsmasq tag 1.3.
20-05-31 08:39:18 ERROR (SyncWorker_3) [supervisor.docker.interface] Can't install homeassistant/amd64-addon-dnsmasq:1.3 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:36727->[::1]:53: read: connection refused").
20-05-31 08:39:38 INFO (MainThread) [supervisor.addons] Create Home Assistant add-on data folder /data/addons/data/a0d7b954_adguard
20-05-31 08:39:38 INFO (SyncWorker_18) [supervisor.docker.interface] Pull image hassioaddons/adguard-amd64 tag 2.4.0.
20-05-31 08:39:38 ERROR (SyncWorker_18) [supervisor.docker.interface] Can't install hassioaddons/adguard-amd64:2.4.0 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:42649->[::1]:53: read: connection refused").
I think it’s an issue with DNS servers? probably because i uninstalled pihole to switch to adguard?
sudo apt-get update:
Err:1 http://gr.archive.ubuntu.com/ubuntu bionic InRelease
Temporary failure resolving 'gr.archive.ubuntu.com'
Err:2 https://download.docker.com/linux/ubuntu bionic InRelease
Temporary failure resolving 'download.docker.com'
Err:3 http://gr.archive.ubuntu.com/ubuntu bionic-updates InRelease
Temporary failure resolving 'gr.archive.ubuntu.com'
Err:4 http://gr.archive.ubuntu.com/ubuntu bionic-backports InRelease
Temporary failure resolving 'gr.archive.ubuntu.com'
Err:5 http://gr.archive.ubuntu.com/ubuntu bionic-security InRelease
Temporary failure resolving 'gr.archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://gr.archive.ubuntu.com/ubuntu/dists/bionic/InRelease Temporary failure resolving 'gr.archive.ubuntu.com'
W: Failed to fetch http://gr.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Temporary failure resolving 'gr.archive.ubuntu.com'
W: Failed to fetch http://gr.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Temporary failure resolving 'gr.archive.ubuntu.com'
W: Failed to fetch http://gr.archive.ubuntu.com/ubuntu/dists/bionic-security/InRelease Temporary failure resolving 'gr.archive.ubuntu.com'
W: Failed to fetch https://download.docker.com/linux/ubuntu/dists/bionic/InRelease Temporary failure resolving 'download.docker.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
My settings seem to be OK:
netplan ip leases enp5s0f2
# This is private data. Do not parse.
ADDRESS= hassio ip address
NETMASK=255.255.255.0
ROUTER= gateway address
SERVER_ADDRESS= router address
NEXT_SERVER=router address
T1=300
T2=525
LIFETIME=600
DNS=8.8.8.8 1.1.1.1
NTP=216.239.35.0 216.239.35.4
CLIENTID=fff1d600d300020000ab116a9e4afbd8ff2f25
Any clues?
ddoll
June 1, 2020, 10:33pm
13
Same here.
No updates work successful - neither add ons nor core
AdGuard not working any longer - container won’t start.
20-06-01 22:20:53 INFO (SyncWorker_13) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.110.4.
20-06-01 22:20:53 ERROR (SyncWorker_13) [supervisor.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.110.4 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:38664->[::1]:53: read: connection refused").
20-06-01 22:20:53 WARNING (MainThread) [supervisor.homeassistant] Update Home Assistant image fails
20-06-01 22:27:31 INFO (SyncWorker_13) [supervisor.docker.interface] Update image hassioaddons/vscode-amd64:2.2.0 to hassioaddons/vscode-amd64:2.3.0
20-06-01 22:27:31 INFO (SyncWorker_13) [supervisor.docker.interface] Pull image hassioaddons/vscode-amd64 tag 2.3.0.
20-06-01 22:27:31 ERROR (SyncWorker_13) [supervisor.docker.interface] Can't install hassioaddons/vscode-amd64:2.3.0 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:41359->[::1]:53: read: connection refused").
Intel NUC with Docker & Hassio
arch x86_64
chassis desktop
dev false
docker true
hassio true
host_os Ubuntu 18.04.4 LTS
installation_type Home Assistant Supervised
os_name Linux
os_version 5.3.0-46-generic
python_version 3.7.7
supervisor 225
timezone Europe/Berlin
version 0.110.3
virtualenv false
I have this problem after updating to Ubuntu 20. I used a command to set dns manually and it works now but I have to do it via ssh everytime I reboot.
I have the same problem too.
It started after adguard were installed and removed. Something is wrong with the network setting.
Can you add the commands you used to get it to work?
sudo echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf > /dev/null
I just don’t know how to make it permanent…
gerdesj
June 2, 2020, 11:25am
18
On Ubuntu there are several ways to get networking running! Do you have a directory called /etc/netplan with a .yaml flie in it? If so, post the contents here. If not then I have some more questions …
francisp
June 2, 2020, 11:32am
19
I’ve done that multiple times and I always have to enter that command after a reboot.
BTW, did it solved anyones problem?
