Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-14395

171114 7:17:09 [ERROR] mysqld got signal 11

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 10.1, 10.2
    • Fix Version/s: 10.1.30, 10.2.11
    • Component/s: Galera, Replication
    • Labels:
    • Environment:
      3 node MariaDB 10.2.9 Glaera Cluster hosted on Ubuntu 16.04 (xenial)

      Description

      Node 1 of 3-node Galera Cluster restarted after reporting the following error in the Syslog.

      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: 171114  7:17:09 [ERROR] mysqld got signal 11 ;
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: This could be because you hit a bug. It is also possible that this binary
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: or one of the libraries it was linked against is corrupt, improperly built,
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: or misconfigured. This error can also be caused by malfunctioning hardware.
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: We will try our best to scrape up some info that will hopefully help
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: diagnose the problem, but since we have already crashed,
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: something is definitely wrong and this may fail.
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: Server version: 10.2.9-MariaDB-10.2.9+maria~xenial-log
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: key_buffer_size=4194304
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: read_buffer_size=2097152
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: max_used_connections=12
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: max_threads=1002
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: thread_count=50
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: It is possible that mysqld could use up to
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6181569 K  bytes of memory
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: Hope that's ok; if not, decrease some variables in the equation.
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: Thread pointer: 0x7fabc00009a8
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: Attempting backtrace. You can use the following information to find out
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: where mysqld died. If you see no messages after this, something went
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: terribly wrong...
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: stack_bottom = 0x7fc3040a5d18 thread_stack 0x49000
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55fcfc8637ee]
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: /usr/sbin/mysqld(handle_fatal_signal+0x305)[0x55fcfc2fc535]
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc308982390]
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG13mark_xid_doneEmb+0x8b)[0x55fcfc3c90fb]
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: /usr/sbin/mysqld(binlog_background_thread+0x32b)[0x55fcfc3c976b]
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc3089786ba]
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc3080233dd]
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: Trying to get some variables.
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: Some pointers may be invalid and cause the dump to abort.
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: Query (0x0):
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: Connection ID (thread ID): 8
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: Status: NOT_KILLED
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: 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
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      Nov 14 07:17:09 sysnet-uk-1604-db-01 mysqld[4838]: information that should help you find out what is causing the crash.
      Nov 14 07:17:10 sysnet-uk-1604-db-01 systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
      Nov 14 07:17:10 sysnet-uk-1604-db-01 systemd[1]: mariadb.service: Unit entered failed state.
      Nov 14 07:17:10 sysnet-uk-1604-db-01 systemd[1]: mariadb.service: Failed with result 'signal'.
      Nov 14 07:17:15 sysnet-uk-1604-db-01 systemd[1]: mariadb.service: Service hold-off time over, scheduling restart.
      Nov 14 07:17:15 sysnet-uk-1604-db-01 systemd[1]: Stopped MariaDB database server.
      Nov 14 07:17:15 sysnet-uk-1604-db-01 systemd[1]: Starting MariaDB database server...
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              anikitin Andrii Nikitin (Inactive)
              Reporter:
              Dermot.Brereton Dermot Brereton
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: