Skip to content

Instantly share code, notes, and snippets.

@elenst
Created July 16, 2018 08:14
Show Gist options
  • Save elenst/b5a7f87c67f24935b05e5492d2d05120 to your computer and use it in GitHub Desktop.
Save elenst/b5a7f87c67f24935b05e5492d2d05120 to your computer and use it in GitHub Desktop.
180715 17:39:16 [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 https://mariadb.com/kb/en/reporting-bugs
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Server version: 10.3.9-MariaDB-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=19
max_threads=153
thread_count=26
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467396 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f0ed00009a8
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 = 0x7f0f600b5e98 thread_stack 0x49000
/data/bld/10.3-rel/bin/mysqld(my_print_stacktrace+0x29)[0x7f0f8a411339]
/data/bld/10.3-rel/bin/mysqld(handle_fatal_signal+0x33f)[0x7f0f89f4ea7f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f0f893c0890]
[0x7f0f8dc3c725]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f0ed0011715): SELECT col_tinyint, `col_timestamp` FROM table10_innodb_int /* table0_int_autoinc table0_myisam_int table1_innodb_int */ WHERE col_tinyint BETWEEN -19 AND 35 + 2 /**/ AND ( `col_timestamp` IS NULL OR `col_bigint_unsigned` <> RAND( 7 ) ) FOR UPDATE
Connection ID (thread ID): 28
Status: NOT_KILLED
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment