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

mysqld got signal 11

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 10.1.13
    • 10.1.19
    • OTHER
    • None
    • RHEL 6.7, pacemaker, replication
      2.6.32-573.18.1.el6.x86_64
    • 10.1.19

    Description

      The database had many transaction(update) from batch server. Suddenly master server had gone, slave server promote to new maser in replication with pacemker. The master server get the error [ERROR] mysqld got signal 11. About 10 minutes later, slave also shutdown abnormally. It also same error([ERROR] mysqld got signal 11).
      And I used mysqbinlog to fine last SQL. I found similary transaction(same table, same update) in master and slave server.

      I attached detail log(Last SQL using mysqlbinlog in master and slave, mysqld.err)

      Attachments

        1. create_table_20160712.sql
          35 kB
        2. master_last.sql
          16 kB
        3. mdev10347.test
          39 kB
        4. my_cnf.txt
          7 kB
        5. mysql_err.txt
          5 kB
        6. query_result_20160710.txt
          12 kB
        7. slave_last.sql
          16 kB

        Activity

          People

            bar Alexander Barkov
            gks3117 sungwon.han
            Votes:
            1 Vote for this issue
            Watchers:
            7 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.