In addition, when I try to update any HA, hassos or addons through the Hass.io UI panel it fails, usually with a 500 Server Error: Internal Server Error, but somtimes it wont report any errors at all. And then after that, I’m unable to access the Hass.io panel at all. It gives me this error when trying to access it Unable to load the panel source: /api/hassio/app/entrypoint.js.
I’ve tried logging into my RPi using ssh and update that way. But that’s unsuccessul as well.
core-ssh:~# hassio homeassistant restart
Post http://hassio/homeassistant/restart: dial tcp: lookup hassio on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
I thought this might be to do with a bad SD card or corruption. However, I did created a fresh SD install on a different RPi using Hass.io (32 bit). This booted fine, but after restoring my latest snapshot backup, all of the above errors and inability to update HA, hassos and addons have returned with the restore of my last snapshot.
All this seems to have been happening for about the last 5-7 days.
Regarding the 500 error/internal server errors, I don’t have any snapshots available. If I take a snapshot now that I’ve uninstalled node-red and now trying to re-install it (but with this error), will the snapshot be valid?
It really seems like this is a problem introduced in 0.88.2. I, like others with the same issue, am running Hassio and any attempt to update or install an add-on ultimately results in the readline error. For example when attempting to install configurator I get this message but it’s the same one I get attempting to upgrade:
Can't install homeassistant/armv7-addon-configurator:2.1 -> 500 Server Error: Internal Server Error ("readlink /mnt/data/docker/overlay2/l: invalid argument").
I’ve been getting a version of this error on every attempted update since 0.88.2 and am now stuck since I don’t have a recent backup. Everything seems to work okay, just can’t install or upgrade anything. I’m sure there are lots of novice users getting the same error but don’t know how/where to look in the logs to find out why the update isn’t working.
I don’t really think “wipe and restore” is a reasonable option for this so is there a way to report this as a bug against Hassio? We’re scaring away novice users by ignoring problems that occur in the easiest way of running HA (Hassio). Most of us using Hassio are doing so because we don’t know how or can’t invest the time in learning the underlying OS issues with running a HA system. We just want it to work and apparently many of us can’t use the over-the-air system update.
Fair enough, it just seemed like a lot of folks stopped being able to update around then. Either way, I’m one of at least several people (and I’m guessing a fair number more who don’t know how to troubleshoot) with a basically vanilla installation on Hassio that can’t update any further and can’t fix the issue without wiping my system and starting from scratch.
Not sure if this is still helpful, but I was having the same issue as you and using the Pi via WiFi.
My error was:
19-04-04 18:43:23 ERROR (SyncWorker_3) [hassio.docker.interface] Can’t install hassioaddons/grafana-armv7:2.0.2 -> 500 Server Error: Internal Server Error (“Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [ipv6]:53: read udp [something (ipv6?]:43589->[something??]:53: i/o timeout”).
Just connected a cable and the update worked. Just testing now the addons as well.
Don’t think that this is a reasonable solution but from the error I would say that the Docker is expecting to receive the files by Cable and not by WiFi. I would say that this is because it may interrupt the connection with possible Sensors?
My pi is connected via ethernet so unfortunately that’s not my issue. Someone commented on the Github related issue that it seems like a bad Docker DB but no guidance on how to fix it.
If you see this reference to the overlay2 it’s most likely docker filesystem corruption and a wipe and restore from snapshot is your best option. Corruption isn’t something you want to try to fix. You just want to be rid of it.
I’ve tried doing a restore from a snapshot (via “Wipe and restore” from web console) but still have the same issue. Is there some other way to do restore than that?