To be completed by the original poster:
CMS Version
4.0.3
Installation Method
docker
Operating System
windows
Issue
I upgraded v4.0.3 as usual but since doing this mqsql fails to start and is permanently restarting, i shut down and restored back to 4.0.3 but the issue still persists, total newbie here so please be kind!
please see logs below:-
2023-10-13 12:58:20 2023-10-13 11:58:20+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.36-1debian10 started.
2023-10-13 12:58:21 2023-10-13 11:58:21+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
2023-10-13 12:58:21 2023-10-13 11:58:21+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.36-1debian10 started.
2023-10-13 12:58:21 2023-10-13T11:58:21.586646Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-10-13 12:58:21 2023-10-13T11:58:21.603709Z 0 [Note] mysqld (mysqld 5.7.36) starting as process 1 …
2023-10-13 12:58:21 2023-10-13T11:58:21.614354Z 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2023-10-13 12:58:21 2023-10-13T11:58:21.617457Z 0 [Note] InnoDB: PUNCH HOLE support available
2023-10-13 12:58:21 2023-10-13T11:58:21.617578Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-10-13 12:58:21 2023-10-13T11:58:21.617586Z 0 [Note] InnoDB: Uses event mutexes
2023-10-13 12:58:21 2023-10-13T11:58:21.617590Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2023-10-13 12:58:21 2023-10-13T11:58:21.617593Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-10-13 12:58:21 2023-10-13T11:58:21.617601Z 0 [Note] InnoDB: Using Linux native AIO
2023-10-13 12:58:21 2023-10-13T11:58:21.618030Z 0 [Note] InnoDB: Number of pools: 1
2023-10-13 12:58:21 2023-10-13T11:58:21.618369Z 0 [Note] InnoDB: Using CPU crc32 instructions
2023-10-13 12:58:21 2023-10-13T11:58:21.621654Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2023-10-13 12:58:21 2023-10-13T11:58:21.641524Z 0 [Note] InnoDB: Completed initialization of buffer pool
2023-10-13 12:58:21 2023-10-13T11:58:21.647651Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2023-10-13 12:58:21 2023-10-13T11:58:21.768320Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2023-10-13 12:58:21 2023-10-13 11:58:21 0x7f3689ce7740 InnoDB: Assertion failure in thread 139872216971072 in file ut0ut.cc line 921
2023-10-13 12:58:21 InnoDB: We intentionally generate a memory trap.
2023-10-13 12:58:21 InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
2023-10-13 12:58:21 InnoDB: If you get repeated assertion failures or crashes, even
2023-10-13 12:58:21 InnoDB: immediately after the mysqld startup, there may be
2023-10-13 12:58:21 InnoDB: corruption in the InnoDB tablespace. Please refer to
2023-10-13 12:58:21 InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
2023-10-13 12:58:21 InnoDB: about forcing recovery.
2023-10-13 12:58:21 11:58:21 UTC - mysqld got signal 6 ;
2023-10-13 12:58:21 This could be because you hit a bug. It is also possible that this binary
2023-10-13 12:58:21 or one of the libraries it was linked against is corrupt, improperly built,
2023-10-13 12:58:21 or misconfigured. This error can also be caused by malfunctioning hardware.
2023-10-13 12:58:21 Attempting to collect some information that could help diagnose the problem.
2023-10-13 12:58:21 As this is a crash and something is definitely wrong, the information
2023-10-13 12:58:21 collection process might fail.