MySQL Forums
Forum List  »  InnoDB

mysql crash InnoDB: MySQL is trying to perform a consistent read but the read view is not assigned!
Posted by: Pavel Dvořák
Date: October 16, 2018 06:42AM

I was browsing tables using phpMyAdmin
and I got a crash
mysqld 8.0.12 on Debian

018-10-16T12:32:08.732361Z 373 [ERROR] [MY-012856] [InnoDB] InnoDB: MySQL is trying to perform a consistent read but the read view is not assigned!
TRANSACTION 422031803808528, ACTIVE 0 sec fetching rows
mysql tables in use 6, locked 0
0 lock struct(s), heap size 1136, 0 row lock(s)
MySQL thread id 373, OS thread handle 140556314851072, query id 28377 localhost root Opening tables
`ENGINE` AS `Engine`,
`ENGINE` AS `Type`,
`VERSION` AS `Version`,
`ROW_FORMAT` AS `Row_format`,
`AVG_ROW_LENGTH` AS `Avg_row_length`,
`DATA_LENGTH` AS `Data_length`,
`MAX_DATA_LENGTH` AS `Max_data_length`,

2018-10-16T12:32:08.732434Z 373 [ERROR] [MY-000000] [InnoDB] InnoDB: Assertion failure:
InnoDB: thread 140556314851072
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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: about forcing recovery.
12:32: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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67846 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fd56413e9f0
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 = 7fd5d137adc0 thread_stack 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char*, unsigned long)+0x2e) [0x55f7fd1e626e]
/usr/sbin/mysqld(handle_fatal_signal+0x4c1) [0x55f7fc4c1e21]
/lib/x86_64-linux-gnu/ [0x7fd6076c40c0]
/lib/x86_64-linux-gnu/ [0x7fd60595dfff]
/lib/x86_64-linux-gnu/ [0x7fd60595f42a]
/usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0xc3) [0x55f7fd478ef3]
/usr/sbin/mysqld(row_search_mvcc(unsigned char*, page_cur_mode_t, row_prebuilt_t*, unsigned long, unsigned long)+0x3295) [0x55f7fd3f6395]
/usr/sbin/mysqld(ha_innobase::general_fetch(unsigned char*, unsigned int, unsigned int)+0xec) [0x55f7fd2b713c]
/usr/sbin/mysqld(handler::ha_rnd_next(unsigned char*)+0x1cc) [0x55f7fc5b0acc]
/usr/sbin/mysqld(rr_sequential(READ_RECORD*)+0x35) [0x55f7fc3346b5]
/usr/sbin/mysqld(JOIN_CACHE_BNL::join_matching_records(bool)+0x117) [0x55f7fc76aa47]
/usr/sbin/mysqld(JOIN_CACHE::join_records(bool)+0x2e0) [0x55f7fc769bc0]
/usr/sbin/mysqld(sub_select_op(JOIN*, QEP_TAB*, bool)+0x35) [0x55f7fc752945]
/usr/sbin/mysqld(sub_select(JOIN*, QEP_TAB*, bool)+0x84) [0x55f7fc7522e4]
/usr/sbin/mysqld(JOIN::exec()+0x5f9) [0x55f7fc7515e9]
/usr/sbin/mysqld(Sql_cmd_dml::execute_inner(THD*)+0x104) [0x55f7fc3fdf74]
/usr/sbin/mysqld(Sql_cmd_dml::execute(THD*)+0x148) [0x55f7fc405f88]
/usr/sbin/mysqld(mysql_execute_command(THD*, bool)+0x20a0) [0x55f7fc3b8e20]
/usr/sbin/mysqld(mysql_parse(THD*, Parser_state*)+0x350) [0x55f7fc3bcd60]
/usr/sbin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0x2cd1) [0x55f7fc3bfc31]
/usr/sbin/mysqld(do_command(THD*)+0x180) [0x55f7fc3c0720]
/usr/sbin/mysqld(+0xd23668) [0x55f7fc4b5668]
/usr/sbin/mysqld(+0x1ee820f) [0x55f7fd67a20f]
/lib/x86_64-linux-gnu/ [0x7fd6076ba494]
/lib/x86_64-linux-gnu/ [0x7fd605a13acf]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fd5644f1318): is an invalid pointer
Connection ID (thread ID): 373

The manual page at contains
information that should help you find out what is causing the crash.
2018-10-16T12:32:09.405436Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.12) starting as process 23522
2018-10-16T12:32:10.623357Z 0 [System] [MY-010229] [Server] Starting crash recovery...
2018-10-16T12:32:10.623463Z 0 [System] [MY-010232] [Server] Crash recovery finished.

Options: ReplyQuote

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.