Перестал запускается контейнер mysql
Раньше поднимал сборку nginx, mysql(версия 5.7), postgres для разработки. Потом поднял еще один контейнер mysql более новой версии и старый контейнер перестал подниматься. Точнее он поднимается, работает несколько секунд и выключается. Что выдает docker logs mysql:
2021-01-22 01:56:37-03:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.33-1debian10 started.
2021-01-22 01:56:37-03:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2021-01-22 01:56:37-03:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.33-1debian10 started.
mysqld: [Warning] World-writable config file '/etc/mysql/conf.d/my.cnf' is ignored.
2021-01-22T04:56:37.728334Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2021-01-22T04:56:37.729616Z 0 [Note] mysqld (mysqld 5.7.33) starting as process 1 ...
2021-01-22T04:56:37.733815Z 0 [Note] InnoDB: PUNCH HOLE support available
2021-01-22T04:56:37.733830Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-01-22T04:56:37.733834Z 0 [Note] InnoDB: Uses event mutexes
2021-01-22T04:56:37.733837Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2021-01-22T04:56:37.733840Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-01-22T04:56:37.733844Z 0 [Note] InnoDB: Using Linux native AIO
2021-01-22T04:56:37.734574Z 0 [Note] InnoDB: Number of pools: 1
2021-01-22T04:56:37.736144Z 0 [Note] InnoDB: Using CPU crc32 instructions
2021-01-22T04:56:37.737570Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-01-22T04:56:37.748369Z 0 [Note] InnoDB: Completed initialization of buffer pool
2021-01-22T04:56:37.750481Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-01-22T04:56:37.771123Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
2021-01-22 01:56:37 0x7f456cd13740 InnoDB: Assertion failure in thread 139936155121472 in file ut0ut.cc line 921
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
04:56:37 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68196 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
mysqld(my_print_stacktrace+0x2c)[0x561e54ce76bc]
mysqld(handle_fatal_signal+0x501)[0x561e545fe0c1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f456d274730]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7f456cd4f7bb]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f456cd3a535]
mysqld(+0x6c40bf)[0x561e545c50bf]
mysqld(+0x6c449d)[0x561e545c549d]
mysqld(+0x11b303c)[0x561e550b403c]
mysqld(+0x11b366e)[0x561e550b466e]
mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x312)[0x561e550bbf12]
mysqld(+0x11732db)[0x561e550742db]
mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0x37)[0x561e55074b27]
mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x409)[0x561e55049bd9]
mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x13e)[0x561e54fe6e9e]
mysqld(+0x10b7b47)[0x561e54fb8b47]
mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f67)[0x561e54fbc707]
mysqld(+0xf8c9e0)[0x561e54e8d9e0]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x55)[0x561e5464f2f5]
mysqld(+0xbe3346)[0x561e54ae4346]
mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x1dc)[0x561e54ae621c]
mysqld(+0x6f603e)[0x561e545f703e]
mysqld(_Z11mysqld_mainiPPc+0x758)[0x561e545f84e8]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f456cd3c09b]
mysqld(_start+0x2a)[0x561e545eed9a]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2021-01-24 09:21:03-03:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.33-1debian10 started.
2021-01-24 09:21:04-03:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2021-01-24 09:21:04-03:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.33-1debian10 started.
mysqld: [Warning] World-writable config file '/etc/mysql/conf.d/my.cnf' is ignored.
2021-01-24T12:21:04.260280Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2021-01-24T12:21:04.261622Z 0 [Note] mysqld (mysqld 5.7.33) starting as process 1 ...
2021-01-24T12:21:04.265660Z 0 [Note] InnoDB: PUNCH HOLE support available
2021-01-24T12:21:04.265683Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-01-24T12:21:04.265688Z 0 [Note] InnoDB: Uses event mutexes
2021-01-24T12:21:04.265692Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2021-01-24T12:21:04.265695Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-01-24T12:21:04.265698Z 0 [Note] InnoDB: Using Linux native AIO
2021-01-24T12:21:04.266393Z 0 [Note] InnoDB: Number of pools: 1
2021-01-24T12:21:04.267828Z 0 [Note] InnoDB: Using CPU crc32 instructions
2021-01-24T12:21:04.269149Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-01-24T12:21:04.281063Z 0 [Note] InnoDB: Completed initialization of buffer pool
2021-01-24T12:21:04.284289Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-01-24T12:21:04.303934Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
2021-01-24 09:21:04 0x7f7ac4825740 InnoDB: Assertion failure in thread 140165259614016 in file ut0ut.cc line 921
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
12:21:04 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68196 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
mysqld(my_print_stacktrace+0x2c)[0x5602cc9736bc]
mysqld(handle_fatal_signal+0x501)[0x5602cc28a0c1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f7ac4d86730]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7f7ac48617bb]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f7ac484c535]
mysqld(+0x6c40bf)[0x5602cc2510bf]
mysqld(+0x6c449d)[0x5602cc25149d]
mysqld(+0x11b303c)[0x5602ccd4003c]
mysqld(+0x11b366e)[0x5602ccd4066e]
mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x312)[0x5602ccd47f12]
mysqld(+0x11732db)[0x5602ccd002db]
mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0x37)[0x5602ccd00b27]
mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x409)[0x5602cccd5bd9]
mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x13e)[0x5602ccc72e9e]
mysqld(+0x10b7b47)[0x5602ccc44b47]
mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f67)[0x5602ccc48707]
mysqld(+0xf8c9e0)[0x5602ccb199e0]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x55)[0x5602cc2db2f5]
mysqld(+0xbe3346)[0x5602cc770346]
mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x1dc)[0x5602cc77221c]
mysqld(+0x6f603e)[0x5602cc28303e]
mysqld(_Z11mysqld_mainiPPc+0x758)[0x5602cc2844e8]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f7ac484e09b]
mysqld(_start+0x2a)[0x5602cc27ad9a]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
P.S. Судя по всему ошибка указана здесь. Если это так, как мне ее исправить внутри контейнера?
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68196 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.