[MDEV-19607] mysqld got signal 11 Created: 2019-05-27  Updated: 2019-06-05  Resolved: 2019-05-27

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.3.15
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Alexander Feller Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Ubuntu 18.04.2 LTS
MariaDB 10.3.15 database server
Google Cloud instance


Attachments: Text File mariadb_crash.log     File my.cnf    
Issue Links:
Duplicate
is duplicated by MDEV-19490 show tables fails when selecting the ... Closed

 Description   

MariaDB crashed with next info in the log:

Thread pointer: 0x7f18c4137828
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 = 0x7f19484b9da8 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5633385f306e]
/usr/sbin/mysqld(handle_fatal_signal+0x515)[0x56333808f6d5]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f1ca621a890]
/usr/sbin/mysqld(+0xcea231)[0x563338630231]
/usr/sbin/mysqld(_Z17find_schema_tableP3THDPK25st_mysql_const_lex_stringPb+0x55)[0x563337f20c95]
/usr/sbin/mysqld(_Z11open_tablesP3THDRK14DDL_options_stPP10TABLE_LISTPjPP19Sroutine_hash_entryjP19Prelocking_strategy+0xbb3)[0x563337e5ad03]
/usr/sbin/mysqld(_Z30open_normal_and_derived_tablesP3THDP10TABLE_LISTjj+0x5a)[0x563337e5baea]
/usr/sbin/mysqld(_Z18mysqld_list_fieldsP3THDP10TABLE_LISTPKc+0x38)[0x563337f10f98]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x252f)[0x563337ebd6af]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x178)[0x563337ebdbf8]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x212)[0x563337f8e532]
/usr/sbin/mysqld(handle_one_connection+0x3d)[0x563337f8e70d]
/usr/sbin/mysqld(+0xc5a79a)[0x5633385a079a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x7f1ca620f6db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f1ca581188f]



 Comments   
Comment by Elena Stepanova [ 2019-05-27 ]

Thanks for the report. We already have it filed and fixed in MDEV-19490 . The fix will be included in the next 10.3 release.

Generated at Thu Feb 08 08:52:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.