maria-discuss team mailing list archive

[Roberto Spadim <roberto@xxxxxxxxxxxxx>]

full log



180830 12:01:21 mysqld_safe Starting mysqld daemon with databases from
/home/mysql/data/local/
2018-08-30 12:01:21 140393902077824 [Warning] 'THREAD_CONCURRENCY' is
deprecated and will be removed in a future release.
2018-08-30 12:01:21 140393902077824 [Note] /usr/mariadb/mariadb/bin//mysqld
(mysqld 10.1.5-MariaDB-log) starting as process 7861 ...
2018-08-30 12:01:21 140393902077824 [Note] mysqld: Aria engine: starting
recovery
*recovered pages: 0% 3631826282% 0%180830 12:01:21 [ERROR] mysqld got
signal 11 ;     (strange >100% progress???)*
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

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.5-MariaDB-log
key_buffer_size=629145600
read_buffer_size=4194304
max_used_connections=0
max_threads=52
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =
1041422 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 0x48000
mysys/stacktrace.c:247(my_print_stacktrace)[0x7fb001500b0b]
sql/signal_handler.cc:153(handle_fatal_signal)[0x7fb00109adb5]
/lib64/libpthread.so.0(+0x10d00)[0x7fafffc2dd00]
*maria/ma_recovery.c:2142(exec_REDO_LOGREC_CLR_END)[0x7fb0014233b7]*
*maria/ma_recovery.c:588(display_and_apply_record)[0x7fb00142485d]*
*maria/ma_recovery.c:350(maria_apply_log)[0x7fb00142845c]*
*maria/ma_recovery.c:242(maria_recovery_from_log)[0x7fb001428f1e]*
maria/ha_maria.cc:3594(ha_maria_init)[0x7fb001401c2d]
sql/handler.cc:512(ha_initialize_handlerton(st_plugin_int*))[0x7fb00109d518]
sql/sql_plugin.cc:1403(plugin_initialize)[0x7fb000f44e65]
sql/sql_plugin.cc:1675(plugin_init(int*, char**, int))[0x7fb000f45dd2]
sql/mysqld.cc:5064(init_server_components)[0x7fb000e7e7e8]
sql/mysqld.cc:5659(mysqld_main(int, char**))[0x7fb000e811ca]
/lib64/libc.so.6(__libc_start_main+0xf0)[0x7fafff2629f0]
/usr/mariadb/mariadb/bin//mysqld(+0x39dbad)[0x7fb000e75bad]
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.
180830 12:01:22 mysqld_safe mysqld from pid file /home/mysql/pid/local.pid
ended