Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 5.5.35
    • 5.5.40
    • None
    • Debian Wheezy, 64bit, Intel Xeon E5620, 4 GB RAM

    Description

      MariaDB server is randomly crashing when ALTERing a table (adding a column), cannot always reproduce. Table is not useble after the crash and data is lost. Command used before the last crash:
      ALTER TABLE `invoices`
      ADD `proforma_invoice_amount_used` FLOAT NOT NULL,
      COMMENT='';

      Attaching these files:
      syslog.log - crash log from syslog
      global_variables.txt - output from 'show global variables'
      table.txt - altered table original definition
      my.cnf - server config file
      invoices.ibd - idb file from table which was altered
      #sql-6493_f2aac.frm - temporary frm file from table which was altered (the original one was missing)

      Attachments

        1. #sql-6493_f2aac.frm
          10 kB
        2. global_variables.txt
          12 kB
        3. invoices.ibd
          160 kB
        4. my.cnf
          5 kB
        5. syslog.log
          13 kB
        6. syslog2.log
          6 kB
        7. table.txt
          2 kB
        8. table2.txt
          1 kB

        Activity

          Both crashed look like there is a corruption on InnoDB data dictionary that could be caused by HD failure. Can you still repeat this issue with more recent version of MariaDB ?

          jplindst Jan Lindström (Inactive) added a comment - Both crashed look like there is a corruption on InnoDB data dictionary that could be caused by HD failure. Can you still repeat this issue with more recent version of MariaDB ?
          azurit azurit added a comment -

          The last crash was with 5.5.37, we are now running 5.5.38. Crashes are very rare and random so i can't tell if it's still reproducable. Crashes occured on different databases/tables (also on new, which were created after first few crashes) and we are using 'innodb_file_per_table = 1'. Also, server is running on RAID1 array and there is no single error logged in smart of all HDDs.

          azurit azurit added a comment - The last crash was with 5.5.37, we are now running 5.5.38. Crashes are very rare and random so i can't tell if it's still reproducable. Crashes occured on different databases/tables (also on new, which were created after first few crashes) and we are using 'innodb_file_per_table = 1'. Also, server is running on RAID1 array and there is no single error logged in smart of all HDDs.

          I see. Is it possible to test with following change:

          revno: 4224
          committer: Jan Lindström <jplindst@mariadb.org>
          branch nick: 5.5
          timestamp: Fri 2014-07-04 12:25:32 +0300
          message:
          MDEV-5621: Server random crash on ALTER TABLE

          This is not a real fix, instead try to gather additional information
          at the point when dictionary content is not what we expect it to be.

          jplindst Jan Lindström (Inactive) added a comment - I see. Is it possible to test with following change: revno: 4224 committer: Jan Lindström <jplindst@mariadb.org> branch nick: 5.5 timestamp: Fri 2014-07-04 12:25:32 +0300 message: MDEV-5621 : Server random crash on ALTER TABLE This is not a real fix, instead try to gather additional information at the point when dictionary content is not what we expect it to be.
          azurit azurit added a comment -

          Where am i supposed to download that patch? thnx

          azurit azurit added a comment - Where am i supposed to download that patch? thnx

          bzr branch lp:maria/5.5 and build from sources at the moment

          jplindst Jan Lindström (Inactive) added a comment - bzr branch lp:maria/5.5 and build from sources at the moment

          People

            jplindst Jan Lindström (Inactive)
            azurit azurit
            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.