Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1
-
None
-
Debian Jessie, Ubuntu Trusty, Ubuntu 15.10, Ubuntu 16.04
x64 versions of above OSs are affected at least.
Happens on host system and under Docker image
-
10.1.10
Description
Initially discovered in Docker image: https://github.com/docker-library/mariadb/issues/29#issuecomment-152766835
But now it happens to me on Ubuntu 16.04 x64 while MariaDB 10.1 server itself works fine, problem is only with `mysqld --verbose --help`.
Output sample:
root@45cb88e4727e:/# mysqld --verbose --help
|
2015-10-31 19:57:51 140581341714368 [Note] Using unique option prefix 'myisam_recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
|
2015-10-31 19:57:51 140581341714368 [Note] Plugin 'FEEDBACK' is disabled.
|
2015-10-31 19:57:51 140581341714368 [Warning] Could not open mysql.plugin table. Some options may be missing from the help text
|
151031 19:57:51 [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
|
|
|
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.8-MariaDB-1~jessie
|
key_buffer_size=134217728
|
read_buffer_size=2097152
|
max_used_connections=0
|
max_threads=102
|
thread_count=0
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759822 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
|
mysqld(my_print_stacktrace+0x2e)[0x562964b8ed0e]
|
mysqld(handle_fatal_signal+0x34d)[0x5629646d46ad]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7fdba4ad08d0]
|
mysqld(_ZN7sys_varC2EP13sys_var_chainPKcS3_ili16get_opt_arg_type20enum_mysql_show_typexP8PolyLockNS_18binlog_status_enumEPFbPS_P3THDP7set_varEPFbS9_SB_13enum_var_typeES3_+0x10d)[0x5629644d0f2d]
|
mysqld(_ZN17sys_var_pluginvarC1EP13sys_var_chainPKcP13st_plugin_intP16st_mysql_sys_var+0xa3)[0x562964561eb3]
|
mysqld(+0x425162)[0x562964562162]
|
mysqld(+0x425577)[0x562964562577]
|
mysqld(_Z11plugin_initPiPPci+0x92a)[0x562964563d8a]
|
mysqld(+0x3824af)[0x5629644bf4af]
|
mysqld(_Z11mysqld_mainiPPc+0x95f)[0x5629644c477f]
|
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fdba2b82b45]
|
mysqld(+0x37b2cd)[0x5629644b82cd]
|
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.
|