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

MariaDB 10.0.14 crash (signal 11)



    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Incomplete
    • 10.0.14
    • N/A
    • OTHER
    • Gentoo Linux, MariaDB installed by package system (emerge).
      8x Intel E5-2630, 8GB RAM and /var/lib/mysql on SSD harddrive



      our server MariaDB 10.0.14 crashed today, 1 months after upgrade from MySQL 5.1.61, which had 2 years uptime.

      This server contains only 2 databases with low load and total size about 1GB. One database with Magento e-shop database and one with our database (100x InnoDB tables, 1x Memory, 1x CONNECT and 1x TokuDB).

      I think, that it is not related to CONNECT, or TokuDB engine.

      MariaDB crashed during standard mysqldump-based backup proces.

      Below is also backtrace and MySQL process-list 1-3 seconds before crash.

      There was no load, just backup simple InnoDB tables of Magento database.

      Thank you for your help.

      141024  2:21:13 [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
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4272191 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      Thread pointer: 0x0x7fa9570f3008
      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 = 0x7fa954579e28 thread_stack 0x80000
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7fa9634ba020): is an invalid pointer
      Connection ID (thread ID): 328170
      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_me
      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.

      MySQL process list 1-3 seconds before crash.

      | Id     | User            | Host      | db              | Command | Time | State                       | Info                                                               | Progress |
      | 1      | event_scheduler | localhost |                 | Daemon  | 14   | Waiting for next activation |                                                                    | 0.000    |
      | 328170 | root            | localhost | client_cz_new   | Query   | 1    | Sending data                | SELECT /*!40001 SQL_NO_CACHE */ * FROM `ig_cashondelivery_foreign` | 0.000    |
      | 328175 | root            | localhost |                 | Query   | 0    | init                        | show processlist                                                   | 0.000    |
      | 328176 | root            | localhost |                 | Sleep   | 1    |                             |                                                                    | 0.000    |




            elenst Elena Stepanova
            jan.reges Ján Regeš
            0 Vote for this issue
            3 Start watching this issue



              Git Integration

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