[MDEV-11717] MariaDB Crash on Signal 11 Created: 2017-01-03  Updated: 2017-02-13  Resolved: 2017-02-13

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

Type: Bug Priority: Major
Reporter: Sukan Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: crash, kill, need_feedback, restart
Environment:

Red Hat Enterprise Linux Server release 6.6 (Santiago)



 Description   

Mariadb restarted abnormally in the production environment. In the error log, below events are logged.

MariaDB version is 10.1.10-MariaDB-log
 
161230 17:40:10 [ERROR] mysqld got signal 11 ;
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 http://kb.askmonty.org/en/reporting-bugs
 
Thread pointer: 0x0x7f82df2dd008
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 = 0x7f816db10e08 thread_stack 0x48000
(my_addr_resolve failure: fork)
/usr/local/mariadb/bin/mysqld(my_print_stacktrace+0x2e) [0xbfcb7e]
/usr/local/mariadb/bin/mysqld(handle_fatal_signal+0x464) [0x762094]
/lib64/libpthread.so.0() [0x3ba220f710]
/usr/local/mariadb/bin/mysqld() [0x9b61ed]
/usr/local/mariadb/bin/mysqld() [0x9b6543]
/usr/local/mariadb/bin/mysqld() [0x9c6db3]
/usr/local/mariadb/bin/mysqld() [0x940267]
/usr/local/mariadb/bin/mysqld() [0x940cda]
/usr/local/mariadb/bin/mysqld() [0x9bd4e5]
/usr/local/mariadb/bin/mysqld() [0x903a5e]
/usr/local/mariadb/bin/mysqld(handler::ha_index_read_map(unsigned char*, unsigned char const*, unsigned long, ha_rkey_function)+0x172) [0x767ab2]
/usr/local/mariadb/bin/mysqld() [0x6093de]
/usr/local/mariadb/bin/mysqld(sub_select(JOIN*, st_join_table*, bool)+0x121) [0x5ee851]
/usr/local/mariadb/bin/mysqld() [0x5f4c6d]
/usr/local/mariadb/bin/mysqld(JOIN::exec_inner()+0xe5e) [0x6069fe]
/usr/local/mariadb/bin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x28f
) [0x6050cf]
/usr/local/mariadb/bin/mysqld(mysql_multi_update(THD*, TABLE_LIST*, List<Item>*, List<Item>*, Item*, unsigned long long, enum_duplicates, bool, st_select_lex_unit*, st_select_lex*, multi_update**)+0x1b0) [0x64e500]
/usr/local/mariadb/bin/mysqld(mysql_execute_command(THD*)+0x731b) [0x5b680b]
/usr/local/mariadb/bin/mysqld(mysql_parse(THD*, char*, unsigned int, Parser_state*)+0x259) [0x5b8d49]
/usr/local/mariadb/bin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x2397) [0x5bbd67]
/usr/local/mariadb/bin/mysqld(do_command(THD*)+0x2a7) [0x5bc167]
/usr/local/mariadb/bin/mysqld(do_handle_one_connection(THD*)+0x183) [0x68a8f3]
/usr/local/mariadb/bin/mysqld(handle_one_connection+0x42) [0x68ab12]
/lib64/libpthread.so.0() [0x3ba22079d1]
/lib64/libc.so.6(clone+0x6d) [0x3ba1ee89dd]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f7e8aaeb020): is an invalid pointer
Connection ID (thread ID): 159259736
Status: NOT_KILLED

Can we get the exact cause for this restart also is there any work around to avoid these ?



 Comments   
Comment by Elena Stepanova [ 2017-01-04 ]

Is the crash repeatable or was it a one-time thing?
Do you happen to have general log (query log) enabled? If so, it should be easy to find the guilty query – it would be the last one in the log under connection ID 159259736.
The query is apparently an UPDATE on multiple tables.

If the crash isn't repeatable and you cannot locate the query, there isn't much we can say about the cause or a workaround, only that you might want to consider upgrading. 10.1.10 is over a year old, there have been 10 releases since then, and many problems have been fixed.

Comment by Elena Stepanova [ 2017-02-13 ]

Please comment if you have further information on this issue.

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