Couldn't connect to MySQL using default configuration (prod)

[dwisiswant0]

Here are the logs:

backend_1   | Connecting to database
mysql_1     | 2023-12-23 01:35:55+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started.
mysql_1     | 2023-12-23 01:35:55+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
mysql_1     | 2023-12-23 01:35:55+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started.
mysql_1     | '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
mysql_1     | 2023-12-23T01:35:55.735558Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysql_1     | 2023-12-23T01:35:55.736793Z 0 [Note] mysqld (mysqld 5.7.44) starting as process 1 ...
audino_frontend_1 exited with code 0
mysql_1     | 2023-12-23T01:35:55.738908Z 0 [Note] InnoDB: PUNCH HOLE support available
mysql_1     | 2023-12-23T01:35:55.738932Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql_1     | 2023-12-23T01:35:55.738934Z 0 [Note] InnoDB: Uses event mutexes
mysql_1     | 2023-12-23T01:35:55.738935Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
mysql_1     | 2023-12-23T01:35:55.738937Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
mysql_1     | 2023-12-23T01:35:55.738938Z 0 [Note] InnoDB: Using Linux native AIO
mysql_1     | 2023-12-23T01:35:55.739267Z 0 [Note] InnoDB: Number of pools: 1
mysql_1     | 2023-12-23T01:35:55.739696Z 0 [Note] InnoDB: Using CPU crc32 instructions
mysql_1     | 2023-12-23T01:35:55.740559Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
redis_1     | 1:C 23 Dec 2023 01:35:55.213 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1     | 1:C 23 Dec 2023 01:35:55.213 # Redis version=5.0.8, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1     | 1:C 23 Dec 2023 01:35:55.213 # Configuration loaded
mysql_1     | 2023-12-23T01:35:55.744929Z 0 [Note] InnoDB: Completed initialization of buffer pool
mysql_1     | 2023-12-23T01:35:55.746038Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
redis_1     | 1:M 23 Dec 2023 01:35:55.213 * Running mode=standalone, port=6379.
redis_1     | 1:M 23 Dec 2023 01:35:55.213 # Server initialized
redis_1     | 1:M 23 Dec 2023 01:35:55.213 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1     | 1:M 23 Dec 2023 01:35:55.213 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
mysql_1     | 2023-12-23T01:35:55.759632Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
mysql_1     | 2023-12-23 01:35:55 0x7a774f6d5880  InnoDB: Assertion failure in thread 134652852263040 in file ut0ut.cc line 921
mysql_1     | InnoDB: We intentionally generate a memory trap.
mysql_1     | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
mysql_1     | InnoDB: If you get repeated assertion failures or crashes, even
mysql_1     | InnoDB: immediately after the mysqld startup, there may be
mysql_1     | InnoDB: corruption in the InnoDB tablespace. Please refer to
mysql_1     | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
mysql_1     | InnoDB: about forcing recovery.
mysql_1     | 01:35:55 UTC - mysqld got signal 6 ;
mysql_1     | This could be because you hit a bug. It is also possible that this binary
mysql_1     | or one of the libraries it was linked against is corrupt, improperly built,
mysql_1     | or misconfigured. This error can also be caused by malfunctioning hardware.
mysql_1     | Attempting to collect some information that could help diagnose the problem.
mysql_1     | As this is a crash and something is definitely wrong, the information
mysql_1     | collection process might fail.
mysql_1     | 
mysql_1     | key_buffer_size=8388608
mysql_1     | read_buffer_size=131072
mysql_1     | max_used_connections=0
mysql_1     | max_threads=151
mysql_1     | thread_count=0
mysql_1     | connection_count=0
mysql_1     | It is possible that mysqld could use up to 
mysql_1     | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68199 K  bytes of memory
mysql_1     | Hope that's ok; if not, decrease some variables in the equation.
mysql_1     | 
mysql_1     | Thread pointer: 0x0
mysql_1     | Attempting backtrace. You can use the following information to find out
mysql_1     | where mysqld died. If you see no messages after this, something went
mysql_1     | terribly wrong...
mysql_1     | stack_bottom = 0 thread_stack 0x40000
redis_1     | 1:M 23 Dec 2023 01:35:55.214 * Ready to accept connections
mysql_1     | mysqld(my_print_stacktrace+0x3b)[0xf11c0b]
mysql_1     | mysqld(handle_fatal_signal+0x486)[0x79f7d6]
mysql_1     | /lib64/libpthread.so.0(+0xf8c0)[0x7a774f2b88c0]
mysql_1     | /lib64/libc.so.6(gsignal+0x37)[0x7a774d5cb387]
mysql_1     | /lib64/libc.so.6(abort+0x148)[0x7a774d5cca78]
mysql_1     | mysqld[0x76f748]
mysql_1     | mysqld(_ZN2ib5fatalD1Ev+0xfd)[0x10e97cd]
mysql_1     | mysqld[0x11a14c2]
mysql_1     | mysqld[0x11a1a0b]
mysql_1     | mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x208)[0x11ad238]
mysql_1     | mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xe4)[0x115b594]
mysql_1     | mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x42d)[0x112a96d]
mysql_1     | mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x15d)[0x10c892d]
mysql_1     | mysqld[0x1090758]
mysql_1     | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x3996)[0x1094ea6]
mysql_1     | mysqld[0xf5a89f]
mysql_1     | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7f2671]
mysql_1     | mysqld[0xcf2c85]
mysql_1     | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0xcf8fb0]
mysql_1     | mysqld[0x797cc4]
mysql_1     | mysqld(_Z11mysqld_mainiPPc+0xa85)[0x79b4e5]
mysql_1     | /lib64/libc.so.6(__libc_start_main+0xf5)[0x7a774d5b7555]
mysql_1     | mysqld[0x78f154]
mysql_1     | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
mysql_1     | information that should help you find out what is causing the crash.
audino_mysql_1 exited with code 2
backend_1   | Couldn't connect to MySQL: 0/30