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

Damaged binlog index

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.0.20
    • N/A
    • OTHER
    • None
    • AWS EC2 / NixOS / Linux-amd64

    Description

      Few times we got damaged binlog index on two of our servers running MariaDB 10.0.20.

      I can't tell anything exact, but.

      Once index looked fine, but probably included invisible symbols, and none of master command were working (RESET MASTER, SHOW MASTER STATUS).

      Another time index got some binary data (attached). This happened on master and slave (both running the same version - 10.0.20, and have the same config)

      Yet another time index on master has something on the first line and mysqldump --master-data=1/2 caught SIGSEGV permanently:

      # mysqldump --master-data=2 --single-transaction=1 --compact=1 --comments=0 bob_live_tw > /dev/null
      Segmentation fault (core dumped)

      mysqld printed something weird on stderr (attached).

      Attachments

        1. crabbed-master-mysql-bin.index.gz
          160 kB
          Igor Pashev
        2. master-main-stderr.log.gz
          21 kB
          Igor Pashev
        3. slave-main-stderr.log.gz
          28 kB
          Igor Pashev
        4. master-my.cnf
          1 kB
          Igor Pashev

        Activity

          People

            Unassigned Unassigned
            ip1981 Igor Pashev
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.