mrlegend
Chevereto Member
Server:
Ubuntu 22.04
Docker Compose version v2.29.1
Version: 4.1.4 Pure Docker: https://github.com/chevereto/docker/blob/4.0/docs/PURE-DOCKER.md
MariaDB Corruption:
This does not seem to be affecting my installation, but it is making a lot of noise in my logs, so I am trying to gauge if following a basic guide on dropping the recreating this table will pose any risk to my installation.
Healthcheck Error:
I left the compose config as-is in the documentation. I don't really see in the documentation if I need to change anything about the variables.
Neither of these issues is impacting the site, it's just making a mess in the logs, which I would like to clean up so that I can catch actual problems if they arise.
Loving v4 so far, it's extremely fast.
I stayed on v3 far too long since upgrading from the nmtan image seemed impossible.
What I did was swap that image out for the official v3, then backed up the volumes and imported them after setting up the Pure Docker v4 in a fresh environment. So I don't know if that is what caused the MariaDB issues. Any help to get past these last two nagging issues is greatly appreciated.
Ubuntu 22.04
Docker Compose version v2.29.1
Version: 4.1.4 Pure Docker: https://github.com/chevereto/docker/blob/4.0/docs/PURE-DOCKER.md
MariaDB Corruption:
Code:
[ERROR] mariadbd: Table mysql/innodb_table_stats is corrupted. Please drop the table and recreate.
Healthcheck Error:
Code:
[Warning] Access denied for user 'healthcheck'@'::1' (using password: YES)
Code:
test: ["CMD", "healthcheck.sh", "--su-mysql", "--connect"]
Neither of these issues is impacting the site, it's just making a mess in the logs, which I would like to clean up so that I can catch actual problems if they arise.
Loving v4 so far, it's extremely fast.
I stayed on v3 far too long since upgrading from the nmtan image seemed impossible.
What I did was swap that image out for the official v3, then backed up the volumes and imported them after setting up the Pure Docker v4 in a fresh environment. So I don't know if that is what caused the MariaDB issues. Any help to get past these last two nagging issues is greatly appreciated.