Are you certain it’s upgrading to 0.103.4? THere was a fatal error like that in 0.103.1… can you post more of your log? It’s hitting a fatal error and rolling back so more info is needed to help.
19-12-24 07:29:39 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.103.4
19-12-24 07:29:39 INFO (SyncWorker_9) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.102.3 to homeassistant/qemux86-64-homeassistant:0.103.4
19-12-24 07:29:39 INFO (SyncWorker_9) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.103.4.
19-12-24 07:36:08 INFO (SyncWorker_9) [hassio.docker.interface] Stop homeassistant application
19-12-24 07:36:15 INFO (SyncWorker_9) [hassio.docker.interface] Clean homeassistant application
19-12-24 07:36:17 INFO (SyncWorker_2) [hassio.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version 0.103.4
19-12-24 07:36:47 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
19-12-24 07:37:58 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
19-12-24 07:38:03 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
19-12-24 07:41:35 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
19-12-24 07:41:40 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
19-12-24 07:42:45 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
19-12-24 07:43:01 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
19-12-24 07:46:58 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
19-12-24 07:57:00 WARNING (MainThread) [hassio.homeassistant] Don’t wait anymore of Home Assistant startup!
19-12-24 07:57:00 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback!
19-12-24 07:57:00 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.102.3
how/where can I find more verbose log?
As I told before, running the check HA config add-on gave me this:
starting version 3.2.8
[13:17:24] INFO: Don’t worry, this temporary installation is not overwriting your current one.
[13:17:24] INFO: Installing Home Assistant: latest…
[13:17:24] INFO: Please be patient, this might take a few minutes…
WARNING: You are using pip version 19.2.2, however version 19.3.1 is available.
You should consider upgrading via the ‘pip install --upgrade pip’ command.
[13:23:43] INFO: Installed Home Assistant 0.103.4
[13:23:43] INFO: Making a copy of your configuration for checking…
[13:23:44] INFO: Checking your configuration against this version…
[13:56:48] INFO: Configuration check finished - no error found!
AFAICS, there’s something like a timeout… checking the logs during upgrading I can’t see any kind of error, but a certain point the upgrade aborts and then rollback to previous running HA
Any hint?
Found my problem (or at least what seems to be it on the surface). I was looking for what I changed in configuration.yaml in the last days. I commented out the tts: section as I’m not using tts at the moment. Enabled it again and voila the update comes through.
Can’t say I understand what one has to do with the other. No hints in the logs.
well… tried today to upgrade to 0.103.5… same result.
it looks like it’s just the UI that it isn’t starting… checking the log I see everything is up and running… I see my sensors, all the integrations running… no errors
any hint?
ok
i just read docker and ubuntu
since i am running docker & debian and also got a hassio docker image t thought its the same bacause afaik hassio was/is a rpi image.
we never learn to much
Yeah basically none of those things you would do in a normal Linux district apply to hassio. All addons and hassio itself come as docker containers and you don’t/can’t install anything in those containers and anything you install isn’t persistent. That pip error/warning is letting you know something in the docker image is using an old version of pip and can just be ignored.
I also run hassio on debian/docker. (On a NUC). The Hassio Pi image runs in a custom O/S called HassOS which uses build root I think. But any hassio comes as a self contained container and you don’t need to worry about any dependencies…
Ther was an issue with changes to something which caused me to get rollbacks ugrading to this version which may be applicable as you both seem to be upgrading from a version earlier than this.
Specifically: “So I had same problem, moved frontend: to below logging:, and deleted reference to api_password and all good.”