Back
Database not ready error after upgrade to 1.5.4
Hey y'all, I just tried upgrading from 1.4.13 to to 1.5.4 today. I ran the upgrade script and left all the variables unchanged, but the dashboard doesn't load at all
Here are the logs from docker logs appwrite
TypeScript
Worker 1 started successfully
Worker 2 started successfully
Worker 3 started successfully
Worker 4 started successfully
Worker 5 started successfully
Worker 6 started successfully
Worker 7 started successfully
Worker 8 started successfully
Worker 9 started successfully
Worker 10 started successfully
Worker 11 started successfully
Worker 12 started successfully
Database not ready. Retrying connection (1)...
Database not ready. Retrying connection (2)...
Database not ready. Retrying connection (3)...
Database not ready. Retrying connection (4)...
Database not ready. Retrying connection (5)...
Database not ready. Retrying connection (6)...
Database not ready. Retrying connection (7)...
Database not ready. Retrying connection (8)...```
I've tried `docker compose down` then `up` again, as well as with `--remove-orphans`
Any steps I should take to try and fix it?
Thanks!
TL;DR
Issue: Database not ready error after upgrading to 1.5.4, causing the dashboard to not load.
Solution: The error in the logs indicates an issue with InnoDB storage engine compatibility. To resolve this, downgrade MariaDB to version 10.7 or earlier, as upgrading InnoDB after a crash is not supported. Start up and shut down MariaDB 10.7 or earlier, then attempt the upgrade to version 1.5.4 again.Logs for mariadb:
TypeScript
2024-04-16 00:32:46+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.7+maria~ubu2204 started.
2024-04-16 00:32:47+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
2024-04-16 00:32:47+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-04-16 00:32:47+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.7+maria~ubu2204 started.
2024-04-16 00:32:47+00:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade or creating healthcheck users) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
2024-04-16 0:32:47 0 [Note] Starting MariaDB 10.11.7-MariaDB-1:10.11.7+maria~ubu2204 source revision 87e13722a95af5d9378d990caf48cb6874439347 as process 1
2024-04-16 0:32:47 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-04-16 0:32:47 0 [Note] InnoDB: Number of transaction pools: 1
2024-04-16 0:32:47 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-04-16 0:32:47 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2024-04-16 0:32:47 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-04-16 0:32:47 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-16 0:32:47 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-04-16 0:32:47 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.7.8. You must start up and shut down MariaDB 10.7 or earlier.
2024-04-16 0:32:47 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2024-04-16 0:32:47 0 [Note] InnoDB: Starting shutdown...
2024-04-16 0:32:47 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2024-04-16 0:32:47 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-04-16 0:32:47 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2024-04-16 0:32:47 0 [ERROR] Aborting
Database not ready error after upgrade to 1.5.4
