I have HA running as VM on ESX server and MariaDB on Synology NAS. DB is ~3GB in size, so should be quick… but currently I’m over an hour in upgrade process and no signs that it is progressing. All I see is warning in log file, that repeats every minute…
2021-04-08 07:34:29 WARNING (Recorder) [homeassistant.components.recorder.migration] Database is about to upgrade. Schema version: 11
2021-04-08 07:34:29 WARNING (Recorder) [homeassistant.components.recorder.migration] Modifying columns event_data in table events. Note: this can take several minutes on large databases and slow computers. Please be patient!
2021-04-08 07:34:39 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.
2021-04-08 07:35:29 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: recorder
...
2021-04-08 08:37:32 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: recorder
So how much ‘be patient’ means?
BTW:
ha core stats shows 0% CPU consumption
network traffic is almost 0
ESX statistics shows that HA is sitting almost idle
the only reference that something is going on is possibly relatively high IOPS statistic on synology NAS for volume on which MariaDB sits… But there are also some other applications using this volume, so not definitive that this is due to DB upgrade.
@DavidFW1960 i rebooted (prior to doing todays update just to check all was good before proceeding) and the speedtest integration is now broken with 2021.3.4 - and cant even change the host which helped before and now getting a ‘Config flow could not be loaded’ when trying options in integration.
So far it´s working great (besides from Speedtest but that´s already mentioned bu a bunch of others).
The “Developer Tools” and “Supervisor” tabs works just as expected, but “Configuration” doesnt show any text, just the icons. The same goes for every “sub menu” as integrations and such, no text and it´s impossible to know what to do with it. I´ve tried switiching the theme but that doesnt help either.
New automation debugging available only for automations with ID field! Why? Message in UI is incorrect, it says “Only automations defined in automations.yaml are debuggable”. It is not true. ID is problem!
20 minutes and counting. Same as cpuram, NUC with mariadb on Synology.
Confusing thing is that homeassistant.local:8123 responds back in the browser with homeassistant.local refused to connect.
Thought for a while that something was wrong. Could access home-assistant.log though and there every minute a log entry about recorder is written, so I guess schema migration is stil going on.
For those having issues with speedtest, as noted above this appears to be a change by ookla that impacts the third party speedtest-cli python module used by most people.
For those wondering why theirs works, you are either very lucky, or probably using the ookla speedtest binary…
(I don’t believe the problem is HA, just coincidence on timing)
