Skip to content
Back

Mariadb keeps Restarting / Fails to initialize

  • 0
  • Self Hosted
GamingForLiveYT
22 Jun, 2025, 19:48

Ive just setup Appwrite on my docker compose host using the supplied Docker compose commands.

My issue is that the mariadb container keeps restarting and fails to initialize.

From what i can tell this is the log output that keeps repeating (obtainied via docker logs appwrite-mariadb)

TypeScript
2025-06-22 19:43:10+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
2025-06-22 19:43:10+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2025-06-22 19:43:10+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.13+maria~ubu2204 started.
2025-06-22 19:43:10+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2025-06-22 19:43:10 0 [Note] Starting MariaDB 10.11.13-MariaDB-ubu2204 source revision 8fb09426b98583916ccfd4f8c49741adc115bac3 server_uid 6rFEtqglNCMjLoJ3R62nuIRWQ28= as process 1
Cannot find checkpoint record at LSN (1,0x1041fdb)
2025-06-22 19:43:10 0 [ERROR] mysqld: Aria recovery failed. Please run aria_chk -r on all Aria tables (*.MAI) and delete all aria_log.######## files
2025-06-22 19:43:10 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2025-06-22 19:43:10 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2025-06-22 19:43:10 0 [Note] InnoDB: Number of transaction pools: 1
2025-06-22 19:43:10 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2025-06-22 19:43:10 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2025-06-22 19:43:10 0 [Warning] mysqld: io_uring_queue_init() failed with EPERM: sysctl kernel.io_uring_disabled has the value 2, or 1 and the user of the process is not a member of sysctl kernel.io_uring_group. (see man 2 io_uring_setup).
2025-06-22 19:43:10 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
2025-06-22 19:43:10 0 [Note] InnoDB: innodb_buffer_pool_size_max=128m, innodb_buffer_pool_size=128m
2025-06-22 19:43:10 0 [Note] InnoDB: Completed initialization of buffer pool
2025-06-22 19:43:10 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2025-06-22 19:43:10 0 [Note] InnoDB: End of log at LSN=4993802
2025-06-22 19:43:10 0 [Note] InnoDB: 128 rollback segments are active.
2025-06-22 19:43:10 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2025-06-22 19:43:10 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2025-06-22 19:43:10 0 [Note] InnoDB: log sequence number 4993802; transaction id 4966
2025-06-22 19:43:10 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-06-22 19:43:10 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded
2025-06-22 19:43:10 0 [ERROR] Failed to initialize plugins.
2025-06-22 19:43:10 0 [ERROR] Aborting
TL;DR
Issue: Mariadb container keeps restarting and fails to initialize. The log output indicates Aria recovery failure and plugin registration error. Solution: Run `aria_chk -r` on all Aria tables (*.MAI) and delete all `aria_log.########` files. Make sure to address the Aria recovery issue and plugin registration failure.
Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more