matthuisman
commented
3 months ago Pretty sure there is a Kodi setting to wait for network sql on boot
On Sun, 14 Jul 2024, 11:31 Jeremy Daalder, @.***> wrote:
I am having issues with system/container restarts - it seems the Kodi dockers I run (two) sometimes start before the DB is actually ready to connect.
In my compose I have a healthcheck on the db container (MariaDB)
db: image: mariadb:latest container_name: db environment: - PUID=${UID} - PGID=${GUID} - TZ=${TZ} - "MARIADB_ROOT_PASSWORD_HASH=${MARIADB_ROOT_PASSWORD_HASH}" - MARIADB_AUTO_UPGRADE=1 volumes: - ${MARIADB_OFFICIAL_CONF}:/etc/mysql/conf.d - ${MARIADB_OFFICIAL_DATA}:/var/lib/mysql ports: - 3306:3306 restart: unless-stopped # Healthcheck from https://mariadb.org/mariadb-server-docker-official-images-healthcheck-without-mysqladmin/ healthcheck: test: [ "CMD", "healthcheck.sh", "--connect", "--innodb_initialized" ] start_period: 1m start_interval: 10s interval: 1m timeout: 5s retries: 3And the Kodi containers depend on this:
kodi-adults: container_name: kodi-adults image: matthuisman/kodi-headless:Omega depends_on: db: condition: service_healthy environment: - PUID=${UID} - PGID=${GUID} - TZ=${TZ} volumes: - ${KODI_ADULTS_CONFIG}:/config/.kodi:rw # All offset by one to avoid LMS... ports: - 8081:8080 # WebUI - 9091:9090 # Websockets - 9778:9777 # esall interface port restart: unless-stopped...but that is not enough, it seems.
When this happens, I see this in the Kodi logs:
2024-07-12 17:37:06.059 T:182 info
: Running database version Addons33 2024-07-12 17:37:06.062 T:182 info : Running database version ViewModes6 2024-07-12 17:37:06.063 T:182 info : Running database version Textures13 2024-07-12 17:37:06.065 T:182 debug : connect replacing configured host db with resolved host 172.18.0.9 2024-07-12 17:37:06.067 T:182 error : Unable to open database: kodi_music_adults83 [2003](Can't connect to MySQL server on '172.18.0.9:3306' (111)) 2024-07-12 17:37:06.067 T:182 debug : connect replacing configured host db with resolved host 172.18.0.9 2024-07-12 17:37:06.067 T:182 error : Unable to open database: kodi_music_adults82 [2003](Can't connect to MySQL server on '172.18.0.9:3306' (111)) .... 2024-07-12 17:37:06.073 T:182 error : Unable to create new database If I manually restart the containers a few minutes after e.g. a system reboot, then they work as expected and connect to the DB normally (and have been running these for some time now successfully, bar this issue that has appeared in recent months)
I'm struggling to work out a solution here, as docker isn't so great at this sort of thing as far as I can tell, I can't e.g. delay the startup of these, and the MariaDB container must be reporting healthy before it's really ready, I suppose, which allows the Kodi containers to then start.
Ideally there would be a healthcheck on the Kodi containers that actually tested this and restarted themselves if the DB is not actually ready to accept a connection...but I don't think there are tools within that container to check this (e.g. some manual way of checking that db:3306 is connectable)
Any ideas?
— Reply to this email directly, view it on GitHub https://github.com/matthuisman/docker-kodi-headless/issues/57, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABPQAKK2SAIEPSSBVZKAD63ZMG2DXAVCNFSM6AAAAABK2U2WQKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQYDOMJZGYYTEOI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
bossanova808
I am having issues with system/container restarts - it seems the Kodi dockers I run (two) sometimes start before the DB is actually ready to connect.
In my compose I have a healthcheck on the db container (MariaDB)
And the Kodi containers depend on this:
...but that is not enough, it seems.
When this happens, I see this in the Kodi logs:
If I manually restart the containers a few minutes after e.g. a system reboot, then they work as expected and connect to the DB normally (and have been running these for some time now successfully, bar this issue that has appeared in recent months)
I'm struggling to work out a solution here, as docker isn't so great at this sort of thing as far as I can tell, I can't e.g. delay the startup of these, and the MariaDB container must be reporting healthy before it's really ready, I suppose, which allows the Kodi containers to then start.
Ideally there would be a healthcheck on the Kodi containers that actually tested this and restarted themselves if the DB is not actually ready to accept a connection...but I don't think there are tools within that container to check this (e.g. some manual way of checking that
db:3306is connectable)Any ideas?