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

Failing assertion: cset == 0

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.5.8
    • None
    • None
    • Ubuntu 20.04 LTS

    Description

      Nov 19 14:18:22 tsip4 mariadbd[2050099]: 2020-11-19 14:18:22 0x7efe0cecd700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.5.8/storage/innobase/handler/ha_innodb.cc lin>
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: Failing assertion: cset == 0
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: We intentionally generate a memory trap.
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: If you get repeated assertion failures or crashes, even
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: immediately after the mysqld startup, there may be
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: corruption in the InnoDB tablespace. Please refer to
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: about forcing recovery.
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: 2020-11-19 14:18:22 0x7efe84393700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.5.8/storage/innobase/handler/ha_innodb.cc lin>
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: 201119 14:18:22 InnoDB: Failing assertion: cset == 0
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: [ERROR] mysqld got signal 6 ;
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: This could be because you hit a bug. It is also possible that this binary
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: or one of the libraries it was linked against is corrupt, improperly built,
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: or misconfigured. This error can also be caused by malfunctioning hardware.
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: We will try our best to scrape up some info that will hopefully help
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: diagnose the problem, but since we have already crashed,
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: something is definitely wrong and this may fail.
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: We intentionally generate a memory trap.
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: If you get repeated assertion failures or crashes, even
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: immediately after the mysqld startup, there may be
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: corruption in the InnoDB tablespace. Please refer to
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: InnoDB: about forcing recovery.
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: Server version: 10.5.8-MariaDB-1:10.5.8+maria~focal
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: key_buffer_size=134217728
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: read_buffer_size=131072
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: max_used_connections=230
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: max_threads=10242
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: thread_count=231
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: It is possible that mysqld could use up to
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 43653385 K bytes of memory
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: Hope that's ok; if not, decrease some variables in the equation.
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: Thread pointer: 0x7efa58000c58
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: Attempting backtrace. You can use the following information to find out
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: where mysqld died. If you see no messages after this, something went
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: terribly wrong...
      Nov 19 14:18:22 tsip4 mariadbd[2050099]: 2020-11-19 14:18:22 266 [ERROR] [FATAL] InnoDB: Unable to find charset-collation 33
      Nov 19 14:18:23 tsip4 systemd[1]: mariadb@standalone.service: Main process exited, code=killed, status=6/ABRT

      Attachments

        Activity

          People

            Unassigned Unassigned
            hbaragar Henry Baragar
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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