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

Production Database Crash - Mysqld got signal 6

Details

    Description

      Hi,

      We have encountered the MariaDB signal 6 error on production database and DB got crashed. I have provided our DB version and error log.

      Kindly provide the permanent fix for this solution

      mysql Ver 15.1 Distrib 10.2.7-MariaDB, for Linux (x86_64) using readline 5.1

      Nov 12 12:12:54 ks-s301 mysqld: InnoDB: Failing assertion: offsets_rec != NULL
      Nov 12 12:12:54 ks-s301 mysqld: InnoDB: We intentionally generate a memory trap.
      Nov 12 12:12:54 ks-s301 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
      Nov 12 12:12:54 ks-s301 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
      Nov 12 12:12:54 ks-s301 mysqld: InnoDB: immediately after the mysqld startup, there may be
      Nov 12 12:12:54 ks-s301 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
      Nov 12 12:12:54 ks-s301 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
      Nov 12 12:12:54 ks-s301 mysqld: InnoDB: about forcing recovery.
      Nov 12 12:12:54 ks-s301 mysqld: 181112 12:12:54 [ERROR] mysqld got signal 6 ;
      Nov 12 12:12:54 ks-s301 mysqld: This could be because you hit a bug. It is also possible that this binary
      Nov 12 12:12:54 ks-s301 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
      Nov 12 12:12:54 ks-s301 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
      Nov 12 12:12:54 ks-s301 mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
      Nov 12 12:12:54 ks-s301 mysqld: We will try our best to scrape up some info that will hopefully help
      Nov 12 12:12:54 ks-s301 mysqld: diagnose the problem, but since we have already crashed,
      Nov 12 12:12:54 ks-s301 mysqld: something is definitely wrong and this may fail.
      Nov 12 12:12:54 ks-s301 mysqld: Server version: 10.2.7-MariaDB-log
      Nov 12 12:12:54 ks-s301 mysqld: key_buffer_size=134217728
      Nov 12 12:12:54 ks-s301 mysqld: read_buffer_size=131072
      Nov 12 12:12:54 ks-s301 mysqld: max_used_connections=34
      Nov 12 12:12:54 ks-s301 mysqld: max_threads=153
      Nov 12 12:12:54 ks-s301 mysqld: thread_count=21
      Nov 12 12:12:54 ks-s301 mysqld: It is possible that mysqld could use up to
      Nov 12 12:12:54 ks-s301 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467207 K bytes of memory
      Nov 12 12:12:54 ks-s301 mysqld: Hope that's ok; if not, decrease some variables in the equation.
      Nov 12 12:12:54 ks-s301 mysqld: Thread pointer: 0x0
      Nov 12 12:12:54 ks-s301 mysqld: Attempting backtrace. You can use the following information to find out
      Nov 12 12:12:54 ks-s301 mysqld: where mysqld died. If you see no messages after this, something went
      Nov 12 12:12:54 ks-s301 mysqld: terribly wrong...
      Nov 12 12:12:54 ks-s301 mysqld: stack_bottom = 0x0 thread_stack 0x49000
      Nov 12 12:12:55 ks-s301 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7ff4cafb437e]
      Nov 12 12:12:55 ks-s301 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x30d)[0x7ff4ca9f9fad]
      Nov 12 12:12:55 ks-s301 mysqld: /lib64/libpthread.so.0(+0xf100)[0x7ff4c9f66100]

      Attachments

        Issue Links

          is part of

          Bug - A problem which impairs or prevents the functions of the product. MDEV-17489 signal 6

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            danblack Daniel Black added a comment -

            I did a really quick look and this seems to be from a code path associated with innodb persistent stats. Would this be right based on your configuration? Its possibly associated with an `ANALYSE TABLE` query? Was something like that in progress when the server crashed.

            Can you include your configuration file.

            If I'm correct disabling innodb persistent stats will prevent this crash.

            danblack Daniel Black added a comment - I did a really quick look and this seems to be from a code path associated with innodb persistent stats. Would this be right based on your configuration? Its possibly associated with an `ANALYSE TABLE` query? Was something like that in progress when the server crashed. Can you include your configuration file. If I'm correct disabling innodb persistent stats will prevent this crash.
            danblack Daniel Black added a comment -

            Looks like MDEV-13534 base on the assertion and server version.

            danblack Daniel Black added a comment - Looks like MDEV-13534 base on the assertion and server version.

            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.