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

DB restarted due to InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.2

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Incomplete
    • 10.2.17
    • N/A
    • OTHER
    • Linux version 3.10.0-514.10.2.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Fri Mar 3 00:04:05 UTC 2017

    Description

      DB got restarted due to bug and looking for permanent fix for this issue
      I am suspecting this issue since we did not run mysql_upgrade after db upgrade

      DB Version

      Welcome to the MariaDB monitor. Commands end with ; or \g.
      Your MariaDB connection id is 1241
      Server version: 10.2.17-MariaDB-log MariaDB Server

      Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

      Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

      Sep 01 23:46:04 ks-s302.alx.local mysqld[13374]: 2018-09-01 23:46:04 139883731261184 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql
      Sep 01 23:46:04 ks-s302.alx.local mysqld[13374]: 2018-09-01 23:46:04 139883731261184 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: 2018-09-01 23:46:06 0x7f393854d700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.2
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: InnoDB: We intentionally generate a memory trap.
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: InnoDB: If you get repeated assertion failures or crashes, even
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: InnoDB: immediately after the mysqld startup, there may be
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: InnoDB: corruption in the InnoDB tablespace. Please refer to
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: InnoDB: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: InnoDB: about forcing recovery.
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: 180901 23:46:06 [ERROR] mysqld got signal 6 ;
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: This could be because you hit a bug. It is also possible that this binary
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: or one of the libraries it was linked against is corrupt, improperly built,
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: or misconfigured. This error can also be caused by malfunctioning hardware.
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: We will try our best to scrape up some info that will hopefully help
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: diagnose the problem, but since we have already crashed,
      Sep 01 23:46:06 ks-s302.alx.local mysqld[13374]: something is definitely wrong and this may fail.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              s.tausiff@animalytix.com Syed Tausiff
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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