Docker MariaDB is not starting

Need help…!!!

In Docker my Mariadb file is not running, while i click on start it automatically gets stopped within seconds.

need your help community…???

what are the mariadb container logs?

how to check mariadb container logs??

it will be difficult if you don’t know docker commands.

docker logs <container-name>

blind spells you can try to reset mariadb and start fresh

docker rm frappe_docker_devcontainer_mariadb_1
docker volume prune -f

rebuild reopen devcontainer again.

when i type “docker logs container-name” it shows me like this, help me to fix my errors…!!!

Thank You.

I searched google. If you have access to google you can try searching error output you get related to mariadb.

It seems you will not be able to retain data. In that case reset mariadb and re create the development sites.

docker rm frappe_docker_devcontainer_mariadb_1
docker volume prune -f

I have the same issue. This happened twice in a few days. It’s Windows 10 environment with Docker and WSL 2.

Log from frappe_docker_devcontainer_mariadb_1 container is:

[Note] mariadbd (server 10.6.7-MariaDB-1:10.6.7+maria~focal) starting as process 1 ...
[Note] InnoDB: Compressed tables use zlib 1.2.11
[Note] InnoDB: Number of pools: 1
[Note] InnoDB: Using crc32 + pclmulqdq instructions
[Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
[Note] InnoDB: Using Linux native AIO
[Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
[Note] InnoDB: Completed initialization of buffer pool
[Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.7+maria~focal started.
[Note] [Entrypoint]: Switching to dedicated user 'mysql'
[Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.7+maria~focal started.
[Note] [Entrypoint]: MariaDB upgrade not required
[Note] InnoDB: Starting crash recovery from checkpoint LSN=9478075,17436744
[ERROR] InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY before FILE_CHECKPOINT for tablespace 256
[ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
[Note] InnoDB: Starting shutdown...
[ERROR] Plugin 'InnoDB' init function returned error.
[ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
[Note] Plugin 'FEEDBACK' is disabled.
[ERROR] Unknown/unsupported storage engine: InnoDB
[ERROR] Aborting

Day before crash I have following line in log:

[ERROR] mariadbd: Table './_2b7d474e075a2e17/__global_search' is marked as crashed and should be repaired

Please advice :slight_smile:

many people are facing this with their docker dev setup.

the only solution i could find for this situation is reset mariadb data are reinstall site

docker stop <mariadb-container-name>
docker rm <mariadb-container-name>
docker volume rm <mariadb-volume-name>

after this rebuild the devcontainer

permanent solution could be use stable Mariadb image

Thank you! I will try with a different MariaDB image.

Thank You @revant_one,

It worked for me…!!!

Then , this would wipe all the data right?

it will wipe data

I am facing that problem too , we have test demo data setup . and customers are testing in it.
It seems to be Mariadb10 bug , some got effected too .
Thats why i hate mysql/maridb , it have a lot of issues in production all the time.
ErpNext should totally move to PostgresSQL .
I had move all my products to Postgres since 2016.

Any way to fix it without wiping data ? I don’t want to piss potential users out.

I’ve not yet faced it in a critical way where I had to recover data.

Search for the error got me this MySQL InnoDB problems - InnoDB registration fails - Stack Overflow