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

upgrade from 10.1.8 to 10.1.9 crashes server




      Hello Devs.

      After upgrading to 10.1.9 mariadb crashes hard. Downgrade to 10.1.8 solves the issue. Here the crash log.

      2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      2015-11-24 13:48:45 140258989979520 [Note] InnoDB: The InnoDB memory heap is disabled
      2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Memory barrier is not used
      2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Compressed tables use zlib 1.2.8
      2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Using Linux native AIO
      2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Using CPU crc32 instructions
      2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Initializing buffer pool, size = 2.0G
      2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Completed initialization of buffer pool
      2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Highest supported file format is Barracuda.
      2015-11-24 13:48:46 140258989979520 [Note] InnoDB: 128 rollback segment(s) are active.
      2015-11-24 13:48:46 140258989979520 [Note] InnoDB: Waiting for purge to start
      2015-11-24 13:48:46 140258989979520 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1555843502
      2015-11-24 13:48:46 140256120637184 [Note] InnoDB: Dumping buffer pool(s) not yet started
      2015-11-24 13:48:46 140258989979520 [Note] Plugin 'FEEDBACK' is disabled.
      2015-11-24 13:48:46 140258989979520 [Note] Server socket created on IP: ''.
      2015-11-24 13:48:46 140258989979520 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.1.9-MariaDB-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution
      151124 13:48:46 [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.1.9-MariaDB-log
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 59167 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      Thread pointer: 0x0x0
      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 = 0x0 thread_stack 0x48000
      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.{quote}

      Any hints how to solve this?

      thanks and cheers


        Issue Links



              jplindst Jan Lindström (Inactive)
              himpierre Thomas Stein
              1 Vote for this issue
              7 Start watching this issue



                Git Integration

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