報錯日志：
200731 11:12:24 mysqld_safe Starting mysqld daemon with databases from /home/zhsq/mysql-5.5.41/data
200731 11:12:24 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
200731 11:12:24 [Note] Plugin 'FEDERATED' is disabled.
200731 11:12:24 InnoDB: The InnoDB memory heap is disabled
200731 11:12:24 InnoDB: Mutexes and rw_locks use GCC atomic builtins
200731 11:12:24 InnoDB: Compressed tables use zlib 1.2.3
200731 11:12:24 InnoDB: Using Linux native AIO
200731 11:12:24 InnoDB: Initializing buffer pool, size = 128.0M
200731 11:12:24 InnoDB: Completed initialization of buffer pool
200731 11:12:24 InnoDB: highest supported file format is Barracuda.
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
200731 11:12:24 InnoDB: Waiting for the background threads to start
200731 11:12:25 InnoDB: 5.5.41-tokudb-7.5.5 started; log sequence number 0
200731 11:12:25 InnoDB: !!! innodb_force_recovery is set to 6 !!!
Fri Jul 31 11:12:25 2020 TokuFT recovery starting in env /home/zhsq/mysql-5.5.41/data/
Fri Jul 31 11:12:25 2020 TokuFT recovery scanning backward from 487966089
Fri Jul 31 11:12:25 2020 TokuFT recovery bw_end_checkpoint at 487966089 timestamp 1595641783111892 xid 487965956 (bw_newer)
Fri Jul 31 11:12:25 2020 TokuFT recovery bw_begin_checkpoint at 487965956 timestamp 1595641783111310 (bw_between)
Fri Jul 31 11:12:25 2020 TokuFT recovery turning around at begin checkpoint 487965956 time 582
Fri Jul 31 11:12:25 2020 TokuFT recovery starts scanning forward to 487966089 from 487965956 left 133 (fw_between)
/home/tokubuild/builds/build-tokudb-7.5.5/mysql-5.5.41/storage/tokudb/ft-index/ft/serialize/ft-serialize.cc:709 toku_deserialize_ft_from: Assertion `!((r0==0 && checkpoint_lsn_0.lsn > max_acceptable_lsn.lsn) && (r1==0 && checkpoint_lsn_1.lsn > max_acceptable_lsn.lsn))' failed (errno=2)
: No such file or directory
Backtrace: (Note: toku_do_assert=0x0x7f70438e1ba0)
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(_Z19db_env_do_backtraceP8_IO_FILE+0x1b)[0x7f70438e14bb]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(+0x895e3)[0x7f70438e15e3]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(+0x8965d)[0x7f70438e165d]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(_Z24toku_deserialize_ft_fromi10__toku_lsnPP2ft+0x371)[0x7f7043951d51]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(_Z35toku_read_ft_and_store_in_cachefileP9ft_handleP9cachefile10__toku_lsnPP2ft+0x86)[0x7f7043951e76]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(+0xfb02d)[0x7f704395302d]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(_Z28toku_ft_handle_open_recoveryP9ft_handlePKciiP10cachetableP7tokutxn7FILENUM10__toku_lsn+0x2d)[0x7f704395351d]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(+0x111b25)[0x7f7043969b25]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(_Z14tokuft_recoverP13__toku_db_envPFvS0_P7tokutxnEPFvS0_P10cachetableEP10tokuloggerPKcSC_PFiP9__toku_dbPK10__toku_dbtSH_EPFiSE_SH_SH_SH_PFvSH_PvESK_EPFiSE_SE_P9DBT_ARRAYSQ_SH_SH_EPFiSE_SE_SQ_SH_SH_Em+0x200)[0x7f7043984e10]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(+0x12d815)[0x7f7043985815]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(+0x488d2)[0x7f70438a08d2]
/home/zhsq/mysql-5.5.41/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x6b5658]
/home/zhsq/mysql-5.5.41/bin/mysqld[0x5cc4d1]
/home/zhsq/mysql-5.5.41/bin/mysqld(_Z11plugin_initPiPPci+0xaae)[0x5d0d6e]
/home/zhsq/mysql-5.5.41/bin/mysqld[0x5563da]
/home/zhsq/mysql-5.5.41/bin/mysqld(_Z11mysqld_mainiPPc+0x447)[0x557037]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f705df29445]
/home/zhsq/mysql-5.5.41/bin/mysqld[0x519e4d]
Engine status function not available
Memory usage:
Arena 0:
system bytes = 0
in use bytes = 0
Total (incl. mmap):
system bytes = 0
in use bytes = 0
max mmap regions = 0
max mmap bytes = 0
03:12:25 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.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=402653184
read_buffer_size=2097152
max_used_connections=0
max_threads=3000
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 = 12715856 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
/home/zhsq/mysql-5.5.41/bin/mysqld(my_print_stacktrace+0x2e)[0x7c9d7e]
/home/zhsq/mysql-5.5.41/bin/mysqld(handle_fatal_signal+0x481)[0x6b35e1]
/lib64/libpthread.so.0(+0xf6d0)[0x7f705ed286d0]
/lib64/libc.so.6(gsignal+0x37)[0x7f705df3d277]
/lib64/libc.so.6(abort+0x148)[0x7f705df3e968]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(+0x895e8)[0x7f70438e15e8]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(+0x8965d)[0x7f70438e165d]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(_Z24toku_deserialize_ft_fromi10__toku_lsnPP2ft+0x371)[0x7f7043951d51]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(_Z35toku_read_ft_and_store_in_cachefileP9ft_handleP9cachefile10__toku_lsnPP2ft+0x86)[0x7f7043951e76]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(+0xfb02d)[0x7f704395302d]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(_Z28toku_ft_handle_open_recoveryP9ft_handlePKciiP10cachetableP7tokutxn7FILENUM10__toku_lsn+0x2d)[0x7f704395351d]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(+0x111b25)[0x7f7043969b25]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(_Z14tokuft_recoverP13__toku_db_envPFvS0_P7tokutxnEPFvS0_P10cachetableEP10tokuloggerPKcSC_PFiP9__toku_dbPK10__toku_dbtSH_EPFiSE_SH_SH_SH_PFvSH_PvESK_EPFiSE_SE_P9DBT_ARRAYSQ_SH_SH_EPFiSE_SE_SQ_SH_SH_Em+0x200)[0x7f7043984e10]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(+0x12d815)[0x7f7043985815]
/home/zhsq/mysql-5.5.41/lib/plugin/ha_tokudb.so(+0x488d2)[0x7f70438a08d2]
/home/zhsq/mysql-5.5.41/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x6b5658]
/home/zhsq/mysql-5.5.41/bin/mysqld[0x5cc4d1]
/home/zhsq/mysql-5.5.41/bin/mysqld(_Z11plugin_initPiPPci+0xaae)[0x5d0d6e]
/home/zhsq/mysql-5.5.41/bin/mysqld[0x5563da]
/home/zhsq/mysql-5.5.41/bin/mysqld(_Z11mysqld_mainiPPc+0x447)[0x557037]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f705df29445]
/home/zhsq/mysql-5.5.41/bin/mysqld[0x519e4d]
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.
200731 11:12:26 mysqld_safe mysqld from pid file /home/zhsq/mysql-5.5.41/data/netposa/mysql.pid ended
uj5u.com熱心網友回復：
必須有個 -p轉載請註明出處，本文鏈接：https://www.uj5u.com/shujuku/10277.html
標籤：MySQL
上一篇：如何實作游標遍歷功能？