Mysql container keeps restarting after update to v4.1.5

Hi, I cant get mysql container to work.
After updating EE to version 4.1.5, mysql container keeps restarting.
Please help

Output of docker logs services_global-db_1
2020-12-05 05:21:37+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.5.4+maria~focal started.
2020-12-05 05:21:38+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
2020-12-05 05:21:38+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.5.4+maria~focal started.
2020-12-05 5:21:38 0 [Note] mysqld (mysqld 10.5.4-MariaDB-1:10.5.4+maria~focal-log) starting as process 1 …
2020-12-05 5:21:38 0 [Note] InnoDB: Using Linux native AIO
2020-12-05 5:21:38 0 [Note] InnoDB: Uses event mutexes
2020-12-05 5:21:38 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-12-05 5:21:38 0 [Note] InnoDB: Number of pools: 1
2020-12-05 5:21:38 0 [Note] InnoDB: Using generic crc32 instructions
2020-12-05 5:21:38 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2020-12-05 5:21:39 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728
2020-12-05 5:21:39 0 [Note] InnoDB: Completed initialization of buffer pool
2020-12-05 5:21:39 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-12-05 5:21:39 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.2.19.
2020-12-05 5:21:39 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2020-12-05 5:21:39 0 [Note] InnoDB: Starting shutdown…
2020-12-05 5:21:39 0 [ERROR] Plugin ‘InnoDB’ init function returned error.
2020-12-05 5:21:39 0 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
2020-12-05 5:21:39 0 [Note] Plugin ‘FEEDBACK’ is disabled.
2020-12-05 5:21:39 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2020-12-05 5:21:39 0 [ERROR] Aborting

What happens if you try to rebuild the global services?

CD to /opt/easyengine/services

#sudo docker-compose down
#sudo docker-compose pull
#sudo docker-compose up -d

Those commands will shut down the global services, perform a pull just to make sure that all the current images are in fact pulled down and then brings the global services back up.

If that does not solve the problem, the issue is most likely exposed in the containers logs. You can access those logs by first typing docker ps and finding the name of the mysql container. On my setup it is services_global-db_1. Then typing docker logs services_global-db_1 (or whatever your particular container is called). You may need to send the output to a file or into a pager like less. I use Putty and have my buffer set to 2000 lines and can scroll up and look for lines marked with [ERROR].

Hope some of this helps. And if you get log entries that you wish to paste here the group may be able to provide additional insight.

Thank you for taking the time to respond.
After banging my head against all walls, I hired a sysadmin to solve my issue.
Problem was with innodb logging - in the end I couldnt save anything from my db :frowning:
Restored a previous backup and moved on.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.