2024-05-28T02:19:27.542915Z 0 [Warning] option ＇max_allowed_packet＇: unsigned value 107374182400 adjusted to 1073741824
2024-05-28T02:19:27.543104Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2024-05-28T02:19:27.543151Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.44-log) starting as process 21969 ...
2024-05-28T02:19:27.551597Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-05-28T02:19:27.551652Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-05-28T02:19:27.551657Z 0 [Note] InnoDB: Uses event mutexes
2024-05-28T02:19:27.551660Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-05-28T02:19:27.551664Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-05-28T02:19:27.551667Z 0 [Note] InnoDB: Using Linux native AIO
2024-05-28T02:19:27.552181Z 0 [Note] InnoDB: Number of pools: 1
2024-05-28T02:19:27.552343Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-05-28T02:19:27.553905Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2024-05-28T02:19:27.562390Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-28T02:19:27.564789Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-05-28T02:19:27.576524Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file /www/server/data/ibdata1 are 0x4000!
2024-05-28 10:19:27 0x2b3c1d579340 InnoDB: Assertion failure in thread 47537190310720 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.
02:19:27 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=33554432
read_buffer_size=786432
max_used_connections=0
max_threads=500
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 = 807467 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
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0xed381c]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x476)[0x79d686]
/lib64/libpthread.so.0(+0xf630)[0x2b3c1d775630]
/lib64/libc.so.6(gsignal+0x37)[0x2b3c1f0f2387]
/lib64/libc.so.6(abort+0x148)[0x2b3c1f0f3a78]
/www/server/mysql/bin/mysqld[0x76df82]
/www/server/mysql/bin/mysqld(_ZN2ib5fatalD1Ev+0xee)[0x10a088e]
/www/server/mysql/bin/mysqld[0x1153cfd]
/www/server/mysql/bin/mysqld[0x115421c]
/www/server/mysql/bin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x1e8)[0x115f588]
/www/server/mysql/bin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xd5)[0x110f4e5]
/www/server/mysql/bin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x3fd)[0x10dfbdd]
/www/server/mysql/bin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14e)[0x108087e]
/www/server/mysql/bin/mysqld[0x1049488]
/www/server/mysql/bin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x3883)[0x104de03]
/www/server/mysql/bin/mysqld[0xf1a1e8]
/www/server/mysql/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7ee0d1]
/www/server/mysql/bin/mysqld[0xcc4516]
/www/server/mysql/bin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2e0)[0xcca430]
/www/server/mysql/bin/mysqld[0x795e45]
/www/server/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0xd51)[0x799901]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x2b3c1f0de555]
/www/server/mysql/bin/mysqld[0x78d7d4]
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.
2024-05-28T02:19:31.652572Z 0 [Warning] option ＇max_allowed_packet＇: unsigned value 107374182400 adjusted to 1073741824
2024-05-28T02:19:31.652729Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2024-05-28T02:19:31.652773Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.44-log) starting as process 22595 ...
2024-05-28T02:19:31.661280Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-05-28T02:19:31.661323Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-05-28T02:19:31.661327Z 0 [Note] InnoDB: Uses event mutexes
2024-05-28T02:19:31.661331Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-05-28T02:19:31.661335Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-05-28T02:19:31.661340Z 0 [Note] InnoDB: Using Linux native AIO
2024-05-28T02:19:31.661873Z 0 [Note] InnoDB: Number of pools: 1
2024-05-28T02:19:31.662046Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-05-28T02:19:31.663631Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2024-05-28T02:19:31.672096Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-28T02:19:31.674188Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-05-28T02:19:31.686087Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file /www/server/data/ibdata1 are 0x4000!
2024-05-28 10:19:31 0x2ac9bb0e9340 InnoDB: Assertion failure in thread 47045915087680 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.
02:19:31 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=33554432
read_buffer_size=786432
max_used_connections=0
max_threads=500
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 = 807467 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
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0xed381c]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x476)[0x79d686]
/lib64/libpthread.so.0(+0xf630)[0x2ac9bb2e5630]
/lib64/libc.so.6(gsignal+0x37)[0x2ac9bcc62387]
/lib64/libc.so.6(abort+0x148)[0x2ac9bcc63a78]
/www/server/mysql/bin/mysqld[0x76df82]
/www/server/mysql/bin/mysqld(_ZN2ib5fatalD1Ev+0xee)[0x10a088e]
/www/server/mysql/bin/mysqld[0x1153cfd]
/www/server/mysql/bin/mysqld[0x115421c]
/www/server/mysql/bin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x1e8)[0x115f588]
/www/server/mysql/bin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xd5)[0x110f4e5]
/www/server/mysql/bin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x3fd)[0x10dfbdd]
/www/server/mysql/bin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14e)[0x108087e]
/www/server/mysql/bin/mysqld[0x1049488]
/www/server/mysql/bin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x3883)[0x104de03]
/www/server/mysql/bin/mysqld[0xf1a1e8]
/www/server/mysql/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7ee0d1]
/www/server/mysql/bin/mysqld[0xcc4516]
/www/server/mysql/bin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2e0)[0xcca430]
/www/server/mysql/bin/mysqld[0x795e45]
/www/server/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0xd51)[0x799901]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x2ac9bcc4e555]
/www/server/mysql/bin/mysqld[0x78d7d4]
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.
2024-05-28T02:25:20.517559Z 0 [Warning] option ＇max_allowed_packet＇: unsigned value 107374182400 adjusted to 1073741824
2024-05-28T02:25:20.517798Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2024-05-28T02:25:20.517847Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.44-log) starting as process 23319 ...
2024-05-28T02:25:20.526552Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-05-28T02:25:20.526590Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-05-28T02:25:20.526595Z 0 [Note] InnoDB: Uses event mutexes
2024-05-28T02:25:20.526599Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-05-28T02:25:20.526603Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-05-28T02:25:20.526607Z 0 [Note] InnoDB: Using Linux native AIO
2024-05-28T02:25:20.527040Z 0 [Note] InnoDB: Number of pools: 1
2024-05-28T02:25:20.527228Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-05-28T02:25:20.528601Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2024-05-28T02:25:20.542904Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-28T02:25:20.546179Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-05-28T02:25:20.561894Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file /www/server/data/ibdata1 are 0x4000!
2024-05-28 10:25:20 0x2acfa90e0340 InnoDB: Assertion failure in thread 47071382864704 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.
02:25:20 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=33554432
read_buffer_size=786432
max_used_connections=0
max_threads=500
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 = 807467 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
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0xed381c]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x476)[0x79d686]
/lib64/libpthread.so.0(+0xf630)[0x2acfa92dc630]
/lib64/libc.so.6(gsignal+0x37)[0x2acfaac59387]
/lib64/libc.so.6(abort+0x148)[0x2acfaac5aa78]
/www/server/mysql/bin/mysqld[0x76df82]
/www/server/mysql/bin/mysqld(_ZN2ib5fatalD1Ev+0xee)[0x10a088e]
/www/server/mysql/bin/mysqld[0x1153cfd]
/www/server/mysql/bin/mysqld[0x115421c]
/www/server/mysql/bin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x1e8)[0x115f588]
/www/server/mysql/bin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xd5)[0x110f4e5]
/www/server/mysql/bin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x3fd)[0x10dfbdd]
/www/server/mysql/bin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14e)[0x108087e]
/www/server/mysql/bin/mysqld[0x1049488]
/www/server/mysql/bin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x3883)[0x104de03]
/www/server/mysql/bin/mysqld[0xf1a1e8]
/www/server/mysql/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7ee0d1]
/www/server/mysql/bin/mysqld[0xcc4516]
/www/server/mysql/bin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2e0)[0xcca430]
/www/server/mysql/bin/mysqld[0x795e45]
/www/server/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0xd51)[0x799901]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x2acfaac45555]
/www/server/mysql/bin/mysqld[0x78d7d4]
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.
2024-05-28T02:25:24.689051Z 0 [Warning] option ＇max_allowed_packet＇: unsigned value 107374182400 adjusted to 1073741824
2024-05-28T02:25:24.689363Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2024-05-28T02:25:24.689451Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.44-log) starting as process 23945 ...
2024-05-28T02:25:24.697289Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-05-28T02:25:24.697326Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-05-28T02:25:24.697330Z 0 [Note] InnoDB: Uses event mutexes
2024-05-28T02:25:24.697334Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-05-28T02:25:24.697337Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-05-28T02:25:24.697343Z 0 [Note] InnoDB: Using Linux native AIO
2024-05-28T02:25:24.697804Z 0 [Note] InnoDB: Number of pools: 1
2024-05-28T02:25:24.697925Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-05-28T02:25:24.699705Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2024-05-28T02:25:24.708091Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-28T02:25:24.710555Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-05-28T02:25:24.722266Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file /www/server/data/ibdata1 are 0x4000!
2024-05-28 10:25:24 0x2ab200cca340 InnoDB: Assertion failure in thread 46944005956416 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.
02:25:24 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=33554432
read_buffer_size=786432
max_used_connections=0
max_threads=500
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 = 807467 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
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0xed381c]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x476)[0x79d686]
/lib64/libpthread.so.0(+0xf630)[0x2ab200ec6630]
/lib64/libc.so.6(gsignal+0x37)[0x2ab202843387]
/lib64/libc.so.6(abort+0x148)[0x2ab202844a78]
/www/server/mysql/bin/mysqld[0x76df82]
/www/server/mysql/bin/mysqld(_ZN2ib5fatalD1Ev+0xee)[0x10a088e]
/www/server/mysql/bin/mysqld[0x1153cfd]
/www/server/mysql/bin/mysqld[0x115421c]
/www/server/mysql/bin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x1e8)[0x115f588]
/www/server/mysql/bin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xd5)[0x110f4e5]
/www/server/mysql/bin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x3fd)[0x10dfbdd]
/www/server/mysql/bin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14e)[0x108087e]
/www/server/mysql/bin/mysqld[0x1049488]
/www/server/mysql/bin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x3883)[0x104de03]
/www/server/mysql/bin/mysqld[0xf1a1e8]
/www/server/mysql/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7ee0d1]
/www/server/mysql/bin/mysqld[0xcc4516]
/www/server/mysql/bin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2e0)[0xcca430]
/www/server/mysql/bin/mysqld[0x795e45]
/www/server/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0xd51)[0x799901]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x2ab20282f555]
/www/server/mysql/bin/mysqld[0x78d7d4]
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.
2024-05-28T02:25:45.506275Z 0 [Warning] option ＇max_allowed_packet＇: unsigned value 107374182400 adjusted to 1073741824
2024-05-28T02:25:45.506467Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2024-05-28T02:25:45.506514Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.44-log) starting as process 24636 ...
2024-05-28T02:25:45.514186Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-05-28T02:25:45.514225Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-05-28T02:25:45.514229Z 0 [Note] InnoDB: Uses event mutexes
2024-05-28T02:25:45.514233Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-05-28T02:25:45.514237Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-05-28T02:25:45.514241Z 0 [Note] InnoDB: Using Linux native AIO
2024-05-28T02:25:45.514684Z 0 [Note] InnoDB: Number of pools: 1
2024-05-28T02:25:45.516108Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-05-28T02:25:45.517791Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2024-05-28T02:25:45.526155Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-28T02:25:45.528396Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-05-28T02:25:45.540075Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file /www/server/data/ibdata1 are 0x4000!
2024-05-28 10:25:45 0x2abe9e2f1340 InnoDB: Assertion failure in thread 46998186038080 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.
02:25:45 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=33554432
read_buffer_size=786432
max_used_connections=0
max_threads=500
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 = 807467 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
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0xed381c]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x476)[0x79d686]
/lib64/libpthread.so.0(+0xf630)[0x2abe9e4ed630]
/lib64/libc.so.6(gsignal+0x37)[0x2abe9fe6a387]
/lib64/libc.so.6(abort+0x148)[0x2abe9fe6ba78]
/www/server/mysql/bin/mysqld[0x76df82]
/www/server/mysql/bin/mysqld(_ZN2ib5fatalD1Ev+0xee)[0x10a088e]
/www/server/mysql/bin/mysqld[0x1153cfd]
/www/server/mysql/bin/mysqld[0x115421c]
/www/server/mysql/bin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x1e8)[0x115f588]
/www/server/mysql/bin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xd5)[0x110f4e5]
/www/server/mysql/bin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x3fd)[0x10dfbdd]
/www/server/mysql/bin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14e)[0x108087e]
/www/server/mysql/bin/mysqld[0x1049488]
/www/server/mysql/bin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x3883)[0x104de03]
/www/server/mysql/bin/mysqld[0xf1a1e8]
/www/server/mysql/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7ee0d1]
/www/server/mysql/bin/mysqld[0xcc4516]
/www/server/mysql/bin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2e0)[0xcca430]
/www/server/mysql/bin/mysqld[0x795e45]
/www/server/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0xd51)[0x799901]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x2abe9fe56555]
/www/server/mysql/bin/mysqld[0x78d7d4]
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.
2024-05-28T02:25:49.570037Z 0 [Warning] option ＇max_allowed_packet＇: unsigned value 107374182400 adjusted to 1073741824
2024-05-28T02:25:49.570189Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2024-05-28T02:25:49.570234Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.44-log) starting as process 25269 ...
2024-05-28T02:25:49.578720Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-05-28T02:25:49.578758Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-05-28T02:25:49.578762Z 0 [Note] InnoDB: Uses event mutexes
2024-05-28T02:25:49.578766Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-05-28T02:25:49.578770Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-05-28T02:25:49.578776Z 0 [Note] InnoDB: Using Linux native AIO
2024-05-28T02:25:49.579211Z 0 [Note] InnoDB: Number of pools: 1
2024-05-28T02:25:49.579328Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-05-28T02:25:49.580663Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2024-05-28T02:25:49.589449Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-28T02:25:49.591639Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-05-28T02:25:49.603340Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file /www/server/data/ibdata1 are 0x4000!
2024-05-28 10:25:49 0x2b003ee93340 InnoDB: Assertion failure in thread 47280055464768 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.
02:25:49 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=33554432
read_buffer_size=786432
max_used_connections=0
max_threads=500
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 = 807467 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
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0xed381c]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x476)[0x79d686]
/lib64/libpthread.so.0(+0xf630)[0x2b003f08f630]
/lib64/libc.so.6(gsignal+0x37)[0x2b0040a0c387]
/lib64/libc.so.6(abort+0x148)[0x2b0040a0da78]
/www/server/mysql/bin/mysqld[0x76df82]
/www/server/mysql/bin/mysqld(_ZN2ib5fatalD1Ev+0xee)[0x10a088e]
/www/server/mysql/bin/mysqld[0x1153cfd]
/www/server/mysql/bin/mysqld[0x115421c]
/www/server/mysql/bin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x1e8)[0x115f588]
/www/server/mysql/bin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xd5)[0x110f4e5]
/www/server/mysql/bin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x3fd)[0x10dfbdd]
/www/server/mysql/bin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14e)[0x108087e]
/www/server/mysql/bin/mysqld[0x1049488]
/www/server/mysql/bin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x3883)[0x104de03]
/www/server/mysql/bin/mysqld[0xf1a1e8]
/www/server/mysql/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7ee0d1]
/www/server/mysql/bin/mysqld[0xcc4516]
/www/server/mysql/bin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2e0)[0xcca430]
/www/server/mysql/bin/mysqld[0x795e45]
/www/server/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0xd51)[0x799901]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x2b00409f8555]
/www/server/mysql/bin/mysqld[0x78d7d4]
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.
2024-05-28T02:26:04.244572Z 0 [Warning] option ＇max_allowed_packet＇: unsigned value 107374182400 adjusted to 1073741824
2024-05-28T02:26:04.244721Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2024-05-28T02:26:04.244765Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.44-log) starting as process 25911 ...
2024-05-28T02:26:04.254142Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-05-28T02:26:04.254184Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-05-28T02:26:04.254188Z 0 [Note] InnoDB: Uses event mutexes
2024-05-28T02:26:04.254192Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-05-28T02:26:04.254196Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-05-28T02:26:04.254199Z 0 [Note] InnoDB: Using Linux native AIO
2024-05-28T02:26:04.254722Z 0 [Note] InnoDB: Number of pools: 1
2024-05-28T02:26:04.254851Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-05-28T02:26:04.256305Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2024-05-28T02:26:04.265323Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-28T02:26:04.267579Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-05-28T02:26:04.279602Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file /www/server/data/ibdata1 are 0x4000!
2024-05-28 10:26:04 0x2b4ca3c73340 InnoDB: Assertion failure in thread 47608165249856 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.
02:26: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=33554432
read_buffer_size=786432
max_used_connections=0
max_threads=500
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 = 807467 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
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0xed381c]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x476)[0x79d686]
/lib64/libpthread.so.0(+0xf630)[0x2b4ca3e6f630]
/lib64/libc.so.6(gsignal+0x37)[0x2b4ca57ec387]
/lib64/libc.so.6(abort+0x148)[0x2b4ca57eda78]
/www/server/mysql/bin/mysqld[0x76df82]
/www/server/mysql/bin/mysqld(_ZN2ib5fatalD1Ev+0xee)[0x10a088e]
/www/server/mysql/bin/mysqld[0x1153cfd]
/www/server/mysql/bin/mysqld[0x115421c]
/www/server/mysql/bin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x1e8)[0x115f588]
/www/server/mysql/bin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xd5)[0x110f4e5]
/www/server/mysql/bin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x3fd)[0x10dfbdd]
/www/server/mysql/bin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14e)[0x108087e]
/www/server/mysql/bin/mysqld[0x1049488]
/www/server/mysql/bin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x3883)[0x104de03]
/www/server/mysql/bin/mysqld[0xf1a1e8]
/www/server/mysql/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7ee0d1]
/www/server/mysql/bin/mysqld[0xcc4516]
/www/server/mysql/bin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2e0)[0xcca430]
/www/server/mysql/bin/mysqld[0x795e45]
/www/server/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0xd51)[0x799901]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x2b4ca57d8555]
/www/server/mysql/bin/mysqld[0x78d7d4]
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.
2024-05-28T02:26:08.271829Z 0 [Warning] option ＇max_allowed_packet＇: unsigned value 107374182400 adjusted to 1073741824
2024-05-28T02:26:08.271982Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2024-05-28T02:26:08.272027Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.44-log) starting as process 26537 ...
2024-05-28T02:26:08.280878Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-05-28T02:26:08.280926Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-05-28T02:26:08.280930Z 0 [Note] InnoDB: Uses event mutexes
2024-05-28T02:26:08.280934Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-05-28T02:26:08.280938Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-05-28T02:26:08.280942Z 0 [Note] InnoDB: Using Linux native AIO
2024-05-28T02:26:08.281390Z 0 [Note] InnoDB: Number of pools: 1
2024-05-28T02:26:08.281523Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-05-28T02:26:08.283070Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2024-05-28T02:26:08.291792Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-28T02:26:08.294179Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-05-28T02:26:08.307295Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file /www/server/data/ibdata1 are 0x4000!
2024-05-28 10:26:08 0x2ba5ecbcc340 InnoDB: Assertion failure in thread 47991641391936 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.
02:26:08 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=33554432
read_buffer_size=786432
max_used_connections=0
max_threads=500
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 = 807467 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
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0xed381c]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x476)[0x79d686]
/lib64/libpthread.so.0(+0xf630)[0x2ba5ecdc8630]
/lib64/libc.so.6(gsignal+0x37)[0x2ba5ee745387]
/lib64/libc.so.6(abort+0x148)[0x2ba5ee746a78]
/www/server/mysql/bin/mysqld[0x76df82]
/www/server/mysql/bin/mysqld(_ZN2ib5fatalD1Ev+0xee)[0x10a088e]
/www/server/mysql/bin/mysqld[0x1153cfd]
/www/server/mysql/bin/mysqld[0x115421c]
/www/server/mysql/bin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x1e8)[0x115f588]
/www/server/mysql/bin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xd5)[0x110f4e5]
/www/server/mysql/bin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x3fd)[0x10dfbdd]
/www/server/mysql/bin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14e)[0x108087e]
/www/server/mysql/bin/mysqld[0x1049488]
/www/server/mysql/bin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x3883)[0x104de03]
/www/server/mysql/bin/mysqld[0xf1a1e8]
/www/server/mysql/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7ee0d1]
/www/server/mysql/bin/mysqld[0xcc4516]
/www/server/mysql/bin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2e0)[0xcca430]
/www/server/mysql/bin/mysqld[0x795e45]
/www/server/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0xd51)[0x799901]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x2ba5ee731555]
/www/server/mysql/bin/mysqld[0x78d7d4]
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.
