Hi guys, we have the same issue with version 10.1.12. Is this issue in a future release aready fixed?

We have exactly the same setup.

Hi, we have the same issue with 10.1.13 but with Ubuntu 14.04.4 LTS, the same node of our three node Galera cluster has crashed 3 times roughly 3 weeks apart.

Experiencing the same issue on 10.1.17 running on red-hat RHEL 6.6. The stack:

170216 0:00:01 [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.1.17-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=32
max_threads=502
thread_count=22
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 412210 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f52f0bb4008
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 = 0x7f54bc440db8 thread_stack 0x40000
//opt/app/mysql/product/mariadb-10.1.17/bin/mysqld(my_print_stacktrace+0x2e)[0xc0717e]
//opt/app/mysql/product/mariadb-10.1.17/bin/mysqld(handle_fatal_signal+0x4ba)[0x7667ea]
/lib64/libpthread.so.0[0x380520f710]
//opt/app/mysql/product/mariadb-10.1.17/bin/mysqld(_ZN13MYSQL_BIN_LOG16rotate_and_purgeEb+0x101)[0x8428d1]
//opt/app/mysql/product/mariadb-10.1.17/bin/mysqld(_Z20reload_acl_and_cacheP3THDyP10TABLE_LISTPi+0x668)[0x6bbff8]
//opt/app/mysql/product/mariadb-10.1.17/bin/mysqld(_Z21mysql_execute_commandP3THD+0x1343)[0x5b2673]
//opt/app/mysql/product/mariadb-10.1.17/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x2b4)[0x5bac44]
//opt/app/mysql/product/mariadb-10.1.17/bin/mysqld[0x5bacd8]
//opt/app/mysql/product/mariadb-10.1.17/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x14e5)[0x5bcdb5]
//opt/app/mysql/product/mariadb-10.1.17/bin/mysqld(_Z10do_commandP3THD+0x2a7)[0x5be087]
//opt/app/mysql/product/mariadb-10.1.17/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x183)[0x68d2f3]
//opt/app/mysql/product/mariadb-10.1.17/bin/mysqld(handle_one_connection+0x42)[0x68d512]
//opt/app/mysql/product/mariadb-10.1.17/bin/mysqld[0xb09699]
/lib64/libpthread.so.0[0x38052079d1]
/lib64/libc.so.6(clone+0x6d)[0x3804ee88fd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f54b64f3020): flush logs
Connection ID (thread ID): 12787
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=off

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.
170216 00:00:01 mysqld_safe Number of processes running now: 0
170216 00:00:01 mysqld_safe WSREP: not restarting wsrep node automatically
170216 00:00:01 mysqld_safe mysqld from pid file //opt/app/mysql/data/datadir/servername.pid ended

Folks, In light of the number of log-rotation based stalls, crashes I created the workaround in MDEV-11610. The code for it is here https://github.com/MariaDB/server/pull/323. In essence it removes rotation of binary and relays logs from the logrotate script and injects a SET LOCAL SQL_BIN_LOG=0. Error, general, engine and slow query logs are still rotated.

If you have any issues with this patch please note it on the github PR or in MDEV-11610.
If you approve of this intermediary solution please vote for issue MDEV-11610.

Fixed by MDEV-9510.