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

Mariadb 10.3.6 Failing assertion on Docker



    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.3.6
    • 10.3.7
    • None
    • Docker 18.03.1 on windows 10


      I start a new container with Docker compose with Maraidb 10.3.6 and I see all strucutures created on file system (system table), after that the server shut down and this is the report :

      2018-05-12  7:54:11 6 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
      2018-05-12 07:54:13 0x7fb4e104f780  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.3.6/storage/innobase/fil/fil0fil.cc line 759
      InnoDB: Failing assertion: node->modification_counter == node->flush_counter || node->space->purpose == FIL_TYPE_TEMPORARY || srv_fast_shutdown == 2 || !srv_was_started
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mysqld startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/
      InnoDB: about forcing recovery.
      180512  7:54:13 [ERROR] mysqld got signal 6 ;
      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.3.6-MariaDB-1:10.3.6+maria~jessie-log
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 348747 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      Thread pointer: 0x0
      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 0x49000
      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.

      Installation of system tables failed! Examine the logs in
      /var/lib/mysql/ for more information.

      The problem could be conflicting information in an external
      my.cnf files. You can ignore these by doing:

      shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf

      You can also try to start the mysqld daemon with:

      If I try to restart the same server (then without creating mysql data on file system) all works.


        1. 000-start-master.sql
          0.1 kB
        2. docker-compose.yml
          0.7 kB
        3. my.cnf
          0.9 kB

        Issue Links



              marko Marko Mäkelä
              alessandro.fustini Alex Fustini
              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.