Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

handle_fatal_signal (sig=11) in thd_ha_data #129

Closed
RoelVdP opened this issue Dec 28, 2015 · 7 comments
Closed

handle_fatal_signal (sig=11) in thd_ha_data #129

RoelVdP opened this issue Dec 28, 2015 · 7 comments
Assignees

Comments

@RoelVdP
Copy link

RoelVdP commented Dec 28, 2015

+bt
#0  0x00007f6561eca771 in __pthread_kill (threadid=, signo=11) at ../nptl/sysdeps/unix/sysv/linux/pthread_kill.c:61
#1  0x0000000000de45a6 in my_write_core (sig=11) at /git/FB-mysql-5.6-051215/mysys/stacktrace.c:422
#2  0x0000000000a63ed4 in handle_fatal_signal (sig=11) at /git/FB-mysql-5.6-051215/sql/signal_handler.cc:239
#3  
#4  0x0000000000ac1814 in thd_ha_data (thd=0x7f655d99f000, hton=0x0) at /git/FB-mysql-5.6-051215/sql/sql_class.cc:669
#5  0x00000000010c7862 in thd_to_trx_func (thd=0x7f655d99f000) at /git/FB-mysql-5.6-051215/storage/innobase/handler/ha_innodb.cc:2030
#6  0x0000000001102426 in i_s_innodb_buffer_page_fill_table (thd=0x7f655d99f000, tables=0x7f6559460a88) at /git/FB-mysql-5.6-051215/storage/innobase/handler/i_s.cc:5734
#7  0x0000000000b69474 in do_fill_table (thd=0x7f655d99f000, table_list=0x7f6559460a88, join_table=0x7f6559466b10) at /git/FB-mysql-5.6-051215/sql/sql_show.cc:7782
#8  0x0000000000b6983e in get_schema_tables_result (join=0x7f6559465c08, executed_place=PROCESSED_BY_JOIN_EXEC) at /git/FB-mysql-5.6-051215/sql/sql_show.cc:7883
#9  0x0000000000b3de92 in JOIN::prepare_result (this=0x7f6559465c08, columns_list=0x7f65624c2710) at /git/FB-mysql-5.6-051215/sql/sql_select.cc:856
#10 0x0000000000addc97 in JOIN::exec (this=0x7f6559465c08) at /git/FB-mysql-5.6-051215/sql/sql_executor.cc:129
#11 0x0000000000b3e941 in mysql_execute_select (thd=0x7f655d99f000, select_lex=0x7f655d9a29b8, free_join=true) at /git/FB-mysql-5.6-051215/sql/sql_select.cc:1133
#12 0x0000000000b3ec1b in mysql_select (thd=0x7f655d99f000, tables=0x7f6559460a88, wild_num=0, fields=..., conds=0x0, order=0x7f655d9a2b80, group=0x7f655d9a2ab8, having=0x0, select_options=2684619520, result=0x7f6559465be0, unit=0x7f655d9a2360, select_lex=0x7f655d9a29b8) at /git/FB-mysql-5.6-051215/sql/sql_select.cc:1254
#13 0x0000000000b3cd05 in handle_select (thd=0x7f655d99f000, result=0x7f6559465be0, setup_tables_done_option=0) at /git/FB-mysql-5.6-051215/sql/sql_select.cc:126
#14 0x0000000000b1618f in execute_sqlcom_select (thd=0x7f655d99f000, all_tables=0x7f6559460a88, last_timer=0x7f65624c49e0) at /git/FB-mysql-5.6-051215/sql/sql_parse.cc:5858
#15 0x0000000000b0ebc8 in mysql_execute_command (thd=0x7f655d99f000, statement_start_time=0x7f65624c3988, post_parse=0x7f65624c49e0) at /git/FB-mysql-5.6-051215/sql/sql_parse.cc:3244
#16 0x0000000000b18fc8 in mysql_parse (thd=0x7f655d99f000, rawbuf=0x7f6559460010 "SELECT TABLE_NAME,INDEX_NAME,NUMBER_RECORDS,DATA_SIZE,PAGE_STATE,PAGE_TYPE FROM INFORMATION_SCHEMA.INNODB_BUFFER_PAGE", length=117, parser_state=0x7f65624c4330, last_timer=0x7f65624c49e0, async_commit=0x7f65624c49df "") at /git/FB-mysql-5.6-051215/sql/sql_parse.cc:7233
#17 0x0000000000b0adcc in dispatch_command (command=COM_QUERY, thd=0x7f655d99f000, packet=0x7f655db47001 "SELECT TABLE_NAME,INDEX_NAME,NUMBER_RECORDS,DATA_SIZE,PAGE_STATE,PAGE_TYPE FROM INFORMATION_SCHEMA.INNODB_BUFFER_PAGE", packet_length=117) at /git/FB-mysql-5.6-051215/sql/sql_parse.cc:1595
#18 0x0000000000b09690 in do_command (thd=0x7f655d99f000) at /git/FB-mysql-5.6-051215/sql/sql_parse.cc:1071
#19 0x0000000000ad16c0 in do_handle_one_connection (thd_arg=0x7f655d99f000) at /git/FB-mysql-5.6-051215/sql/sql_connect.cc:1071
#20 0x0000000000ad0fbf in handle_one_connection (arg=0x7f655d99f000) at /git/FB-mysql-5.6-051215/sql/sql_connect.cc:929
#21 0x00007f6561ec5df5 in start_thread (arg=0x7f65624c5700) at pthread_create.c:308
#22 0x00007f655ff191ad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Testcase:
mysql> SELECT TABLE_NAME,INDEX_NAME,NUMBER_RECORDS,DATA_SIZE,PAGE_STATE,PAGE_TYPE FROM INFORMATION_SCHEMA.INNODB_BUFFER_PAGE;
ERROR 2013 (HY000): Lost connection to MySQL server during query

Server started with these options:
--no-defaults --default-tmp-storage-engine=MyISAM --rocksdb --skip-innodb --default-storage-engine=RocksDB

This bug is partly blocking QA efforts as it is seen in many trials. Thank you.

@hermanlee
Copy link
Contributor

The problem looks to be the innodb plugin is disabled, but the innodb_* plugins for information schema are all still running, so requests through information schema for innodb status can cause the system to crash.

Could you disable the buffer_page plugin on startup with --skip-innodb-buffer-page for your tests? The other plugins look to function without crashing in the absence of innodb.

@RoelVdP
Copy link
Author

RoelVdP commented Dec 28, 2015

@hermanlee sure can do! Thank you! Will update if I still see similar crashes after using --skip-innodb-buffer-page. Thanks

@jkedgar jkedgar self-assigned this Jan 15, 2016
@jkedgar
Copy link
Contributor

jkedgar commented Jan 19, 2016

jkedgar added a commit that referenced this issue Jan 19, 2016
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

#129

Test Plan: MTR with new test that attempts to SELECT from all INNODB INFORMATION_SCHEMA tables with InnoDB disabled.

Reviewers: hermanlee4, yoshinorim

Reviewed By: yoshinorim

Subscribers: webscalesql-eng

Differential Revision: https://reviews.facebook.net/D52959
@jkedgar jkedgar closed this as completed Jan 19, 2016
@RoelVdP
Copy link
Author

RoelVdP commented Jan 19, 2016

@hermanlee @jkedgar Thanks. Does this mean I should be able to remove --skip-innodb-buffer-page from default test setup? Thank you

@jkedgar
Copy link
Contributor

jkedgar commented Jan 19, 2016

Yes. It will now get a warning that the table is not available when InnoDB is not present, but it will no longer crash without that flag.

@RoelVdP
Copy link
Author

RoelVdP commented Jan 19, 2016

Thank you @jkedgar

@RoelVdP
Copy link
Author

RoelVdP commented Feb 1, 2016

--skip-innodb-buffer-page was removed from all tests

george-lorch pushed a commit to george-lorch/percona-server that referenced this issue May 7, 2016
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook/mysql-5.6#129

Test Plan: MTR with new test that attempts to SELECT from all INNODB INFORMATION_SCHEMA tables with InnoDB disabled.

Reviewers: hermanlee4, yoshinorim

Reviewed By: yoshinorim

Subscribers: webscalesql-eng

Differential Revision: https://reviews.facebook.net/D52959
george-lorch pushed a commit to george-lorch/percona-server that referenced this issue May 9, 2016
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook/mysql-5.6#129

Test Plan: MTR with new test that attempts to SELECT from all INNODB INFORMATION_SCHEMA tables with InnoDB disabled.

Reviewers: hermanlee4, yoshinorim

Reviewed By: yoshinorim

Subscribers: webscalesql-eng

Differential Revision: https://reviews.facebook.net/D52959
hermanlee pushed a commit that referenced this issue Jan 31, 2017
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

#129

Test Plan: MTR with new test that attempts to SELECT from all INNODB INFORMATION_SCHEMA tables with InnoDB disabled.

Reviewers: hermanlee4, yoshinorim

Reviewed By: yoshinorim

Subscribers: webscalesql-eng

Differential Revision: https://reviews.facebook.net/D52959
VitaliyLi pushed a commit to VitaliyLi/mysql-5.6 that referenced this issue Feb 9, 2017
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Test Plan: MTR with new test that attempts to SELECT from all INNODB INFORMATION_SCHEMA tables with InnoDB disabled.

Reviewers: hermanlee4, yoshinorim

Reviewed By: yoshinorim

Subscribers: webscalesql-eng

Differential Revision: https://reviews.facebook.net/D52959
facebook-github-bot pushed a commit that referenced this issue Dec 23, 2019
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

#129

Differential Revision: https://reviews.facebook.net/D52959

fbshipit-source-id: 3ac0a37
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Aug 12, 2020
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959

fbshipit-source-id: 3ac0a37
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Sep 9, 2020
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959

fbshipit-source-id: 3ac0a37
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Sep 16, 2020
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959

fbshipit-source-id: 3ac0a37
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Oct 5, 2020
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959

fbshipit-source-id: 3ac0a37
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Nov 11, 2020
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959

fbshipit-source-id: 3ac0a37
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Mar 11, 2021
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959

fbshipit-source-id: 3787173e8ff
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Aug 16, 2021
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959

fbshipit-source-id: 3787173e8ff
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Aug 30, 2021
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959

fbshipit-source-id: 3787173e8ff
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Aug 30, 2021
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959

fbshipit-source-id: 3787173e8ff
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Sep 1, 2021
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959

fbshipit-source-id: 3787173e8ff
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Sep 2, 2021
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959

fbshipit-source-id: 3787173e8ff
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Jan 17, 2022
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959
ldonoso pushed a commit to ldonoso/percona-server that referenced this issue Mar 15, 2022
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook/mysql-5.6#129

Differential Revision: https://reviews.facebook.net/D52959
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Apr 26, 2022
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue May 20, 2022
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959
laurynas-biveinis pushed a commit to laurynas-biveinis/mysql-5.6 that referenced this issue Aug 11, 2022
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Mar 28, 2023
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Jun 1, 2023
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959
inikep pushed a commit to inikep/mysql-5.6 that referenced this issue Jun 14, 2023
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook#129

Differential Revision: https://reviews.facebook.net/D52959
inikep pushed a commit to inikep/percona-server that referenced this issue Apr 9, 2024
Summary:
Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault.  Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled.

facebook/mysql-5.6#129

Differential Revision: https://reviews.facebook.net/D52959
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants