[MDEV-12040] Frequent crashes Created: 2017-02-09  Updated: 2017-03-12  Resolved: 2017-03-12

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

Type: Bug Priority: Major
Reporter: Craig Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

Linux 4.8.13-1-ARCH #1 SMP PREEMPT Fri Dec 9 07:24:34 CET 2016 x86_64 GNU/Linux

Intel Corporation Atom processor C2000 SoC Transaction Router



 Description   

Feb 09 16:22:56  mysqld[23505]: 170209 16:22:56 [ERROR] mysqld got signal 11 ;
Feb 09 16:22:56  mysqld[23505]: This could be because you hit a bug. It is also possible that this binary
Feb 09 16:22:56  mysqld[23505]: or one of the libraries it was linked against is corrupt, improperly built,
Feb 09 16:22:56  mysqld[23505]: or misconfigured. This error can also be caused by malfunctioning hardware.
Feb 09 16:22:56  mysqld[23505]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Feb 09 16:22:56  mysqld[23505]: We will try our best to scrape up some info that will hopefully help
Feb 09 16:22:56  mysqld[23505]: diagnose the problem, but since we have already crashed,
Feb 09 16:22:56  mysqld[23505]: something is definitely wrong and this may fail.
Feb 09 16:22:56  mysqld[23505]: Server version: 10.1.20-MariaDB
Feb 09 16:22:56  mysqld[23505]: key_buffer_size=16777216
Feb 09 16:22:56  mysqld[23505]: read_buffer_size=262144
Feb 09 16:22:56  mysqld[23505]: max_used_connections=3
Feb 09 16:22:56  mysqld[23505]: max_threads=153
Feb 09 16:22:56  mysqld[23505]: thread_count=3
Feb 09 16:22:56  mysqld[23505]: It is possible that mysqld could use up to
Feb 09 16:22:56  mysqld[23505]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 137009 K  bytes of memory
Feb 09 16:22:56  mysqld[23505]: Hope that's ok; if not, decrease some variables in the equation.
Feb 09 16:22:56  mysqld[23505]: Thread pointer: 0x0x7fe2883bbf08
Feb 09 16:22:56  mysqld[23505]: Attempting backtrace. You can use the following information to find out
Feb 09 16:22:56  mysqld[23505]: where mysqld died. If you see no messages after this, something went
Feb 09 16:22:56  mysqld[23505]: terribly wrong...

Feb 09 16:22:56  mysqld[23505]: stack_bottom = 0x7fe28bcf8178 thread_stack 0x48400
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55b138341c0e]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x55b137e7ee7d]
Feb 09 16:22:56  mysqld[23505]: /usr/lib/libpthread.so.0(+0x11080)[0x7fe289e19080]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(_ZN4JOIN4execEv+0x11)[0x55b137d4dd01]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(_ZN30subselect_single_select_engine4execEv+0x8e)[0x55b137f03b2e]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(_ZN14Item_subselect4execEv+0x3c)[0x55b137f036ac]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(_ZN21Item_exists_subselect8val_boolEv+0x31)[0x55b137f03431]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(_ZN20sp_instr_jump_if_not9exec_coreEP3THDPj+0x2a)[0x55b137f7fbfa]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0x30a)[0x55b137f84d8a]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x75e)[0x55b137f80fee]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x712)[0x55b137f82792]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x2e72)[0x55b137cf2e02]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x321)[0x55b137cf9341]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x242c)[0x55b137cfc69c]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(_Z10do_commandP3THD+0x194)[0x55b137cfcde4]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1d2)[0x55b137dc62c2]
Feb 09 16:22:56  mysqld[23505]: /usr/sbin/mysqld(handle_one_connection+0x40)[0x55b137dc6430]
Feb 09 16:22:56  mysqld[23505]: /usr/lib/libpthread.so.0(+0x7454)[0x7fe289e0f454]
Feb 09 16:22:56  mysqld[23505]: /usr/lib/libc.so.6(clone+0x5f)[0x7fe2894c67df]
Feb 09 16:22:56  mysqld[23505]: Trying to get some variables.
Feb 09 16:22:59  systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
Feb 09 16:22:59  systemd[1]: mariadb.service: Unit entered failed state.
Feb 09 16:22:59  systemd[1]: mariadb.service: Failed with result 'signal'.



 Comments   
Comment by Elena Stepanova [ 2017-02-10 ]

There are several open bug reports which have similar stack traces, e.g. MDEV-7339, MDEV-11230, MDEV-7826, and some more.
Without the actual query and/or a better stack trace it's impossible to say which one is the closest.
If it happens frequently, could you maybe locate the query? According to the log, you don't have much concurrency on the server, so maybe you could enable general_log till the next occurrence?

Comment by Elena Stepanova [ 2017-03-12 ]

Please comment to re-open if you have more information on the issue.

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