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

MariaDB 10.0.14 Galera node shutdown with signal 11




      The Galera cluster consists of 2 data nodes and one Galera Arbitrator.
      The cluster has been up and running with 10.0.14 since "141105 5:41:15"

      141116  0:51:17 [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.0.14-MariaDB-wsrep-log
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 238333 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      Thread pointer: 0x0x7f69f568d008
      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 = 0x7f69dabb5c78 thread_stack 0x48000
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f69db022020): is an invalid pointer
      Connection ID (thread ID): 32
      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
      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.
      141116 00:51:25 mysqld_safe Number of processes running now: 0
      141116 00:51:25 mysqld_safe WSREP: not restarting wsrep node automatically
      141116 00:51:25 mysqld_safe mysqld from pid file /data/lib/mysql/SESAMMALSQL02.pid ended

      The crashed node was kept down for memory chips check.
      After the crash, the only live Galera node started time to time to respond to the application with Primary key duplicate errors.
      Due to that error, a decision for restarting the garbd instance has been taken.
      On the garbd stop the only node lost the quorum and refused new connections, so had to be restarted with bootstrapping a new cluster.


        1. my.cnf
          9 kB
        2. mysql.log
          981 kB

        Issue Links



              nirbhay_c Nirbhay Choubey (Inactive)
              ivan.stoykov@skysql.com Stoykov (Inactive)
              0 Vote for this issue
              5 Start watching this issue



                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.