Problem with MariaDB-database over night

Configuration
1

Hello,

over night (i didnt make any update as far as I know), ha showed the following problems:

Setup of recorder is taking over 10 seconds.

Error during connection setup: (MySQLdb.OperationalError) (2002, “Can’t connect to server on ‘core-mariadb’ (115)”) (Background on this error at: Error Messages — SQLAlchemy 2.0 Documentation) (retrying in 3 seconds)

Unable to prepare setup for platform ‘history_stats.sensor’: (DependencyError(…), ‘Could not setup dependencies: recorder’)

  • Unable to set up dependencies of ‘history_stats’. Setup failed for dependencies: recorder

  • Unable to set up dependencies of ‘logbook’. Setup failed for dependencies: recorder

  • Unable to set up dependencies of ‘history’. Setup failed for dependencies: recorder

  • Unable to set up dependencies of ‘energy’. Setup failed for dependencies: history, recorder

  • Unable to set up dependencies of ‘default_config’. Setup failed for dependencies: energy, history, logbook

  • Setup failed for ‘recorder’: Integration failed to initialize.

  • Setup failed for ‘logbook’: (DependencyError(…), ‘Could not setup dependencies: recorder’)

  • Setup failed for ‘history’: (DependencyError(…), ‘Could not setup dependencies: recorder’)

  • Setup failed for ‘energy’: (DependencyError(…), ‘Could not setup dependencies: history, recorder’)

  • Setup failed for ‘default_config’: (DependencyError(…), ‘Could not setup dependencies: energy, history, logbook’)

Any ideas to resolve this? I already switched back to an old backup, but it shows the same problem. My guess is any kind of update it made automatically and now I have these problems, fearing loosing all my database.

Thanks for any help!

1 Like
2

Hello Nuklearhase,

does your MariaDB add-on auto-update?

There is an issue with updating MariaDB to version 2.7.0.
Read MariaDB is not starting after update to 2.7.0.

I have had the same problem.
After stopping the add-on, restoring the previous version from backup, restarting ha, stopping add-on, upgrading to version 2.7.0 again, the problem is solved.
In the meanwhile version 2.7.1 is released.