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

Upgrading problems from MariaDb 10.10.1 to 10.10.2

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.10.2
    • N/A
    • Upgrades
    • Linux Ubuntu 20.04, na

    Description

      We have downloaded the recent MariaDB 10.10.2 version for some testings and tried to upgrade from 10.10.1 to 10.10.2. The upgrade miserably failed:

      mariadb-upgrade --user=root --force
      Error: Server version (10.10.1-MariaDB-log) does not match with the version of
      the server (10.10.2-MariaDB) with which this program was built/distributed. You can
      use --skip-version-check to skip this check.
      FATAL ERROR: Upgrade failed

      then

      mariadb-upgrade --user=root --force --skip-version-check
      ERROR 1728 (HY000) at line 837: Cannot load from mysql.proc. The table is probably corrupted

      and

      mariadb-upgrade --user=root
      This installation of MariaDB is already upgraded to 10.10.1-MariaDB.
      There is no need to run mysql_upgrade again for 10.10.2-MariaDB.
      You can use --force if you still want to run mysql_upgrade

      Attachments

        Activity

          This message would normally be issued if the mariadb-upgrade binary that you are running is from 10.10.2, but mariadbd it connects to is still 10.10.1. Can you verify that it's not the case?
          Maybe the server package didn't upgrade on some reason, or the binary didn't get replaced, or the server did not get restarted after the upgrade.

          elenst Elena Stepanova added a comment - This message would normally be issued if the mariadb-upgrade binary that you are running is from 10.10.2, but mariadbd it connects to is still 10.10.1. Can you verify that it's not the case? Maybe the server package didn't upgrade on some reason, or the binary didn't get replaced, or the server did not get restarted after the upgrade.

          Hi Elena

          Your argument about not restarting the server seems quite valid. Also the original error message, when I read it again, says the same.
          I cannot reproduce it any more now because I restarted the daemon and re-initialized the database.

          So makes sense to close this issue.

          Sorry for bothering you!

          oli Oli Sennhauser added a comment - Hi Elena Your argument about not restarting the server seems quite valid. Also the original error message, when I read it again, says the same. I cannot reproduce it any more now because I restarted the daemon and re-initialized the database. So makes sense to close this issue. Sorry for bothering you!

          oli,

          Thanks for the confirmation. If you still have the syslog from the time of upgrade, maybe we could try to understand why the server wasn't restarted. Assuming it's a deb package installation, the restart is supposed to happen automatically, so it's somewhat worrisome if it didn't.

          elenst Elena Stepanova added a comment - oli , Thanks for the confirmation. If you still have the syslog from the time of upgrade, maybe we could try to understand why the server wasn't restarted. Assuming it's a deb package installation, the restart is supposed to happen automatically, so it's somewhat worrisome if it didn't.

          Hello Elena

          That is easy to explain: It was a Layer-8 error which caused the not-starting of the mariadbd!
          It is NOT a DEB package but a binary tarball. In combination with Layer-8 problems this is disastrous!
          But I will attach the error log anyway...

          oli Oli Sennhauser added a comment - Hello Elena That is easy to explain: It was a Layer-8 error which caused the not-starting of the mariadbd! It is NOT a DEB package but a binary tarball. In combination with Layer-8 problems this is disastrous! But I will attach the error log anyway...
          elenst Elena Stepanova added a comment - - edited

          Thanks, I see.
          Indeed, there is no indication of any attempt, failed or not, to shut down in the error log at the time when upgrade occurred, so apparently some integration is missing.

          elenst Elena Stepanova added a comment - - edited Thanks, I see. Indeed, there is no indication of any attempt, failed or not, to shut down in the error log at the time when upgrade occurred, so apparently some integration is missing.

          People

            Unassigned Unassigned
            oli Oli Sennhauser
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.