Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.5.16
-
None
-
None
-
None
-
centos 7.6
Description
kill mysqld during the pquery test,then restart.
During the restart, a core dump occurs and the restart fails repeatedly.
error log:
2022-09-14 17:55:58 0 [Note] /sda/percona//5.7_dev/sql/bin/mysqld (mysqld 10.5.16-MariaDB-debug) starting as process 85613 ...
2022-09-14 17:55:58 0 [Note] mysqld: Aria engine: starting recovery
recovered pages: 0% 10% 22% 32% 51% 70% 85% 97% 100% (0.0 seconds); tables to flush: 1 0
(0.1 seconds);
2022-09-14 17:55:58 0 [Note] mysqld: Aria engine: recovery done
2022-09-14 17:55:58 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2022-09-14 17:55:58 0 [Note] InnoDB: Uses event mutexes
2022-09-14 17:55:58 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2022-09-14 17:55:58 0 [Note] InnoDB: Number of pools: 1
2022-09-14 17:55:58 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-09-14 17:55:58 0 [Note] InnoDB: Using Linux native AIO
2022-09-14 17:55:58 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2022-09-14 17:55:58 0 [Note] InnoDB: Completed initialization of buffer pool
2022-09-14 17:55:58 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=13911854,13911854
2022-09-14 17:55:58 0 [Note] InnoDB: Ignoring data file './test/#sql-ib43.ibd' with space ID 28. Another data file called ./test/t5.ibd exists with the same space ID.
2022-09-14 17:55:58 0 [ERROR] InnoDB: Table test/#sql-ib43 in InnoDB data dictionary has tablespace id 28, but the tablespace with that id has name test/t5. Have you deleted or moved .ibd files?
2022-09-14 17:55:58 0 [Note] InnoDB: Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2022-09-14 17:55:58 0 [ERROR] InnoDB: Trying to open table `test`.`#sql-ib43` with id 28, conflicting with `test`.`t5`
2022-09-14 17:55:58 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 5 row operations to undo
2022-09-14 17:55:58 0 [Note] InnoDB: Trx id counter is 1202
2022-09-14 17:55:58 0 [Note] InnoDB: Starting final batch to recover 423 pages from redo log.
2022-09-14 17:56:02 0 [Note] InnoDB: 128 rollback segments are active.
2022-09-14 17:56:02 0 [ERROR] InnoDB: Table test/t5 in InnoDB data dictionary has tablespace id 28, but the tablespace with that id has name test/#sql-ib43. Have you deleted or moved .ibd files?
2022-09-14 17:56:02 0 [Note] InnoDB: Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2022-09-14 17:56:02 0 [ERROR] InnoDB: Trying to open table `test`.`t5` with id 28, conflicting with `test`.`#sql-ib43`
mysqld: /data/fuxi_ci_workspace/631930990b59023190ebac9a/storage/innobase/row/row0uins.cc:387: bool row_undo_ins_parse_undo_rec(undo_node_t*, bool): Assertion `dict_table_is_file_per_table(table) == !is_system_tablespace(table->space_id)' failed.
220914 17:56:02 [ERROR] 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.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
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.
Server version: 10.5.16-MariaDB-debug
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2333779 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 = 0x0 thread_stack 0x49000
mysys/stacktrace.c:212(my_print_stacktrace)[0x55f8545a6add]
sql/signal_handler.cc:225(handle_fatal_signal)[0x55f853ca5a90]
sigaction.c:0(__restore_rt)[0x7fceb2c1f6d0]
:0(__GI_raise)[0x7fceb2879277]
:0(__GI_abort)[0x7fceb287a968]
:0(__assert_fail_base)[0x7fceb2872096]
:0(_GI__assert_fail)[0x7fceb2872142]
row/row0uins.cc:389(row_undo_ins_parse_undo_rec(undo_node_t*, bool))[0x55f8544e8594]
row/row0uins.cc:532(row_undo_ins(undo_node_t*, que_thr_t*))[0x55f8544e8af5]
row/row0undo.cc:420(row_undo(undo_node_t*, que_thr_t*))[0x55f8542dac55]
row/row0undo.cc:476(row_undo_step(que_thr_t*))[0x55f8542daeca]
que/que0que.cc:944(que_thr_step(que_thr_t*))[0x55f85421d879]
que/que0que.cc:1008(que_run_threads_low(que_thr_t*))[0x55f85421db28]
que/que0que.cc:1050(que_run_threads(que_thr_t*))[0x55f85421dd8a]
trx/trx0roll.cc:631(trx_rollback_active(trx_t*))[0x55f8543422b7]
trx/trx0roll.cc:784(trx_rollback_recovered(bool))[0x55f854342bde]
srv/srv0start.cc:1780(srv_start(bool))[0x55f854301469]
handler/ha_innodb.cc:4075(innodb_init(void*))[0x55f8540cc389]
sql/handler.cc:645(ha_initialize_handlerton(st_plugin_int*))[0x55f853ca8320]
sql/sql_plugin.cc:1461(plugin_initialize(st_mem_root*, st_plugin_int*, int*, char**, bool))[0x55f8539619ce]
sql/sql_plugin.cc:1753(plugin_init(int*, char**, int))[0x55f8539627c0]
sql/mysqld.cc:4929(init_server_components())[0x55f853807e3d]
sql/mysqld.cc:5523(mysqld_main(int, char**))[0x55f853808f99]
sql/main.cc:25(main)[0x55f8537fe335]
??:0(__libc_start_main)[0x7fceb2865445]
??:0(_start)[0x55f8537fe259]
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /sda/percona/5.7_dev/tmp/933190/77/data
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size unlimited unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 7000 7000 processes
Max open files 80000 80000 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 2570482 2570482 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: core-%e-%u-%s-%t-%h
core:
(gdb) bt
#0 0x00007fceb2c1ca01 in pthread_kill () from /lib64/libpthread.so.0
#1 0x000055f8545a6bcf in my_write_core (sig=6) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/mysys/stacktrace.c:424
#2 0x000055f853ca5dd6 in handle_fatal_signal (sig=6) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/sql/signal_handler.cc:344
#3 <signal handler called>
#4 0x00007fceb2879277 in raise () from /lib64/libc.so.6
#5 0x00007fceb287a968 in abort () from /lib64/libc.so.6
#6 0x00007fceb2872096 in __assert_fail_base () from /lib64/libc.so.6
#7 0x00007fceb2872142 in __assert_fail () from /lib64/libc.so.6
#8 0x000055f8544e8594 in row_undo_ins_parse_undo_rec (node=0x55f8566def48, dict_locked=true)
at /data/fuxi_ci_workspace/631930990b59023190ebac9a/storage/innobase/row/row0uins.cc:387
#9 0x000055f8544e8af5 in row_undo_ins (node=0x55f8566def48, thr=0x55f8566c8da8)
at /data/fuxi_ci_workspace/631930990b59023190ebac9a/storage/innobase/row/row0uins.cc:532
#10 0x000055f8542dac55 in row_undo (node=0x55f8566def48, thr=0x55f8566c8da8)
at /data/fuxi_ci_workspace/631930990b59023190ebac9a/storage/innobase/row/row0undo.cc:420
#11 0x000055f8542daeca in row_undo_step (thr=0x55f8566c8da8) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/storage/innobase/row/row0undo.cc:476
#12 0x000055f85421d879 in que_thr_step (thr=0x55f8566c8da8) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/storage/innobase/que/que0que.cc:944
#13 0x000055f85421db28 in que_run_threads_low (thr=0x55f8566c8da8) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/storage/innobase/que/que0que.cc:1008
#14 0x000055f85421dd8a in que_run_threads (thr=0x55f8566c8da8) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/storage/innobase/que/que0que.cc:1048
#15 0x000055f8543422b7 in trx_rollback_active (trx=0x7fceb00f51b8) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/storage/innobase/trx/trx0roll.cc:628
#16 0x000055f854342bde in trx_rollback_recovered (all=false) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/storage/innobase/trx/trx0roll.cc:783
#17 0x000055f854301469 in srv_start (create_new_db=false) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/storage/innobase/srv/srv0start.cc:1775
#18 0x000055f8540cc389 in innodb_init (p=0x55f855c76848) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/storage/innobase/handler/ha_innodb.cc:4075
#19 0x000055f853ca8320 in ha_initialize_handlerton (plugin=0x55f855c40450) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/sql/handler.cc:645
#20 0x000055f8539619ce in plugin_initialize (tmp_root=0x7ffda68dfbd0, plugin=0x55f855c40450, argc=0x55f85523c5e8 <remaining_argc>, argv=0x55f855bf4830,
options_only=false) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/sql/sql_plugin.cc:1461
#21 0x000055f8539627c0 in plugin_init (argc=0x55f85523c5e8 <remaining_argc>, argv=0x55f855bf4830, flags=0)
at /data/fuxi_ci_workspace/631930990b59023190ebac9a/sql/sql_plugin.cc:1753
#22 0x000055f853807e3d in init_server_components () at /data/fuxi_ci_workspace/631930990b59023190ebac9a/sql/mysqld.cc:4929
#23 0x000055f853808f99 in mysqld_main (argc=48, argv=0x55f855bf4830) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/sql/mysqld.cc:5523
#24 0x000055f8537fe335 in main (argc=47, argv=0x7ffda68e1578) at /data/fuxi_ci_workspace/631930990b59023190ebac9a/sql/main.cc:25
Attachments
Issue Links
- relates to
-
MDEV-24323 Crash on recovery after server kill during instant ADD COLUMN
- Closed