Musl 1.1.20-r0 does not work with MariaDB > 10.2.x
This affects alpine edge. Latest upgrade upgraded musl 1.1.20-r0, which then caused MariaDB to fail to start. I was able to also reproduce with fresh install of alpine and simply running /etc/init.d/mariadb setup which then produced error:
180910 15:54:37 [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
key_buffer_size=1048576
read_buffer_size=2097152
max_used_connections=0
max_threads=153
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 631108 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x555d6e6a6c68
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...
Cannot determine thread, fp=0x49000, backtrace may not be correct.
Bogus stack limit or frame pointer, fp=0x49000, stack_bottom=0x7f64147d0000, thread_stack=299008, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0): is an invalid pointer
Connection ID (thread ID): 6
Status: NOT_KILLED
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
Downgrading to previous version by adding repository and running: apk add “musl=1.1.19-r10” allows MariaDB to start as before.
(from redmine: issue id 9407, created on 2018-09-10, closed on 2019-05-04)
- Changesets:
- Revision cd3bc80a by Kaarle Ritvanen on 2018-09-18T16:23:51Z:
main/mariadb: work around pthread_detach issue
https://jira.mariadb.org/browse/MDEV-17200
fixes #9407