Closed paboman closed 6 months ago
agners
commented
6 months ago Hm yeah I did not try the modify json approach myself, and I can imagine that under Windows the outcome might not work :cry:
But there are many ways to solve the issue.
So in what state are you now exactly (what does the log show)?
Only after stopping the add on the backup completes correctly.
This sounds like a different issue altogether, which probably warrants investigation on it's own.
thorian93
commented
6 months ago I hope this is not considered spam, but I just have to say it: Although the situation is at least inconvenient, the mechanisms of Home Assistant enable us to recover rather easily and with minimal data loss for most installations, that face(d) this issue. But what I want to point out in particular, is the tremendous support of one individual here: @agners, thanks a ton! :heart: It is people like him going out of their way to help and guide, which strengthens my belief and commitment to the open source community. Cheers mate!
MilorES
commented
6 months ago There is no way in HAos to go to the previous plugin version or choose one (would be ideal).
I can somehow edit something to make it...
Even if it means losing the data, it would be deleting the plugin and deleting something, right?
agners
commented
6 months ago There is no way in HAos to go to the previous plugin version or choose one (would be ideal).
There is a difference between plug-in and add-on: Plug-ins (e.g. DNS,Audio or CLI plug-in) extend Supervisor functionality and are tighly managed by Supervisor. For these, there are no backups. However, you can downgrade these from the console, e.g.:
ha cli update --version 2024.04.0But you are probably referring to add-ons. Add-ons can only be downgraded through backups. This is currently a limitation of add-ons. Technically, the main problem is that our add-on repositories only carry the metadata of the add-ons of the latest version :cry: Backups do have the metadata of the older version included. That is why it is possible to go back to an older version by (partially) restoring an older backup.
voncaron
commented
6 months ago Thx. for all of the information here. After 6 hours of restore time for 2.6.1 I finally migrated to 2.7.1! What I figured out is that you need to be patience and enough disk space is also needed. For me it was 50 GB to extract the tar file in tmp folder under backup and additional 120GB to extract the gz file to data folder - 170GB in total. So free disk space is really needed if you have a big database.
MilorES
commented
6 months ago There is no way in HAos to go to the previous plugin version or choose one (would be ideal).
There is a difference between plug-in and add-on: Plug-ins (e.g. DNS,Audio or CLI plug-in) extend Supervisor functionality and are tighly managed by Supervisor. For these, there are no backups. However, you can downgrade these from the console, e.g.:
ha cli update --version 2024.04.0But you are probably referring to add-ons. Add-ons can only be downgraded through backups. This is currently a limitation of add-ons. Technically, the main problem is that our add-on repositories only carry the metadata of the add-ons of the latest version 😢 Backups do have the metadata of the older version included. That is why it is possible to go back to an older version by (partially) restoring an older backup.
My backup was deleted... so I'll have to start again.
Do I have to delete something after uninstalling to start over? (In case there is a mariadb folder or volume left)
Note: It would be nice to be able to mark the backups with the last copy of the plugin or a number, so that not everything counts as backups (I guess that's why it was deleted).
Note: From now on I will mark the backup of the mariadb and nginx addonas as backups not to be deleted
quizzical86
commented
6 months ago I have the errors: ERROR (Recorder) [homeassistant.components.recorder.core] Error during connection setup MySQLdb.OperationalError: (2002, "Can't connect to server on 'core-mariadb' (115)")
I make regular backups using samba backup, but for unclear reasons it does not include mariadb. So I also seem stuck.
How do I get back to having my home assistant working again? Can I at least keep my long term statistics somehow? I'm having difficulty understanding how to do about it. I've been trying these docker commands listed above but difficult as I'm on HassOS. I tried with Portainer but failed.
MilorES
commented
6 months ago If you use HAos you have to recover the previous copy of mariadb. When it is working again, you have to stop the container, wait a few minutes (to confirm that it is stopped), update.
If you do not have the backup, you have to delete the plugin, restart and install again (configure).
tsloms
commented
1 month ago Can you restore 2.6.1 again, then try the following command to stop the add-on before updating in the Advanced SSH & Web Terminal (from the community store)
docker stop --time 300 addon_core_mariadb
`s6-rc: info: service legacy-services successfully started s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service mariadb-post: stopping [10:02:43] INFO: Deleting service information from Home Assistant
s6-rc: info: service mariadb-post successfully stopped s6-rc: info: service mariadb-core: stopping 2024-09-22 10:02:55 0 [Note] mysqld (initiated by: unknown): Normal shutdown 2024-09-22 10:02:55 0 [Note] InnoDB: FTS optimize thread exiting. 2024-09-22 10:03:32 0 [Note] InnoDB: Starting shutdown... 2024-09-22 10:03:32 0 [Note] InnoDB: Dumping buffer pool(s) to /data/databases/ib_buffer_pool 2024-09-22 10:03:32 0 [Note] InnoDB: Restricted to 2028 pages due to innodb_buf_pool_dump_pct=25 2024-09-22 10:03:32 0 [Note] InnoDB: Buffer pool(s) dump completed at 240922 10:03:32 2024-09-22 10:04:43 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2024-09-22 10:04:43 0 [Note] InnoDB: Shutdown completed; log sequence number 249878547097; transaction id 10118414 2024-09-22 10:04:49 0 [Note] mysqld: Shutdown complete
[10:04:50] INFO: Service mariadb exited with code 0 (by signal 0) s6-rc: info: service mariadb-core successfully stopped s6-rc: info: service mariadb-pre: stopping s6-rc: info: service mariadb-pre successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped`
Took a little longe for me and I had to add sudo before the command:
sudo docker stop --time 300 addon_core_mariadb
Describe the issue you are experiencing
what should i do ?
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
MariaDB
What is the version of the add-on?
2.7.0
Steps to reproduce the issue
1.update from 2.6.1 to 2.7.0
System Health information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4885 Installed Version | 1.34.0 Stage | running Available Repositories | 1402 Downloaded Repositories | 17Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.2 -- | -- update_channel | stable supervisor_version | supervisor-2024.04.0 agent_version | 1.6.0 docker_version | 25.0.5 disk_total | 30.8 GB disk_used | 7.4 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | File editor (5.8.0), Terminal & SSH (9.13.0), Mosquitto broker (6.4.0), Zigbee2MQTT (1.36.1-1), MariaDB (2.7.0), Samba share (12.3.1), Ring-MQTT with Video Streaming (5.6.3), Studio Code Server (5.15.0), Node-RED (17.0.11)Dashboards
dashboards | 2 -- | -- resources | 8 views | 9 mode | storageSonoff
version | 3.6.0 (8dd8af9) -- | -- cloud_online | 1 / 2 local_online | 1 / 1Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
No response