maria-discuss team mailing list archive

[Brian Evans <grknight@xxxxxxxxxxxxxx>]

On 6/2/2016 8:50 AM, Niklaas Baudet von Gersdorff wrote:
>
> 160602 14:32:22 [ERROR] mysqld got signal 6 ;
> 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.1.13-MariaDB
> key_buffer_size=0
> read_buffer_size=131072
> max_used_connections=0
> max_threads=153
> thread_count=0
> It is possible that mysqld could use up to 
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 335983 K  bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
>
> Thread pointer: 0x0x0
> 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 = 0x0 thread_stack 0x48400
> 0xafa3de <my_print_stacktrace+0x2e> at /usr/local/libexec/mysqld
> 0x72004e <handle_fatal_signal+0x22e> at /usr/local/libexec/mysqld
> 0x8031e9b4a <pthread_sigmask+0x51a> at /lib/libthr.so.3
> 0x8031e922c <pthread_getspecific+0xe1c> at /lib/libthr.so.3
> The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
> information that should help you find out what is causing the crash.
> 160602 14:32:22 mysqld_safe mysqld from pid file /var/db/mysql/mariadb1.box-hlm-01.klaas.pid ended
>
> -------------------->8--------------------
>
> Is there an error in the configuration?
>
> Any help is very much appreciated.

This is https://jira.mariadb.org/browse/MDEV-9757

Brian