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

mysql_upgrade_service throws exception upgrading from 10.0 to 10.3

Details

    Description

      We have MariaDB x64 10.0.19 running on Windows Server R2. I ran the MardiaDB 10.3.14 install. I chose the "upgrade" option, defaults everywhere, and the install went fine, except the final upgrade tool threw an exception. If I go to "c:\program files\mariadb 10.3\bin" and run "mysql_upgrade_service --service=MySQL, then it throws an exception on phase 3/10, ensuring innodb slow shutdown.

      Attached is a minidump crash report.

      Attachments

        Activity

          BenYokoK Ben 136 added a comment -

          Crash report shows:
          > KERNELBASE.dll!WriteFile() Unknown
          kernel32.dll!WriteFileImplementation() Unknown
          MYSQL_UPGRADE_SERVICE.EXE!000000013f511952() Unknown
          MYSQL_UPGRADE_SERVICE.EXE!000000013f511f54() Unknown
          MYSQL_UPGRADE_SERVICE.EXE!000000013f532344() Unknown

          BenYokoK Ben 136 added a comment - Crash report shows: > KERNELBASE.dll!WriteFile() Unknown kernel32.dll!WriteFileImplementation() Unknown MYSQL_UPGRADE_SERVICE.EXE!000000013f511952() Unknown MYSQL_UPGRADE_SERVICE.EXE!000000013f511f54() Unknown MYSQL_UPGRADE_SERVICE.EXE!000000013f532344() Unknown
          BenYokoK Ben 136 added a comment -

          I have a full dump as well, but it is too large to attach. The crash is a null pointer write.

          The wiki and web site provide no instructions for what to do when this fails...

          BenYokoK Ben 136 added a comment - I have a full dump as well, but it is too large to attach. The crash is a null pointer write. The wiki and web site provide no instructions for what to do when this fails...

          Well, this is a bug, which seems to happen only on quite old Windows versions now. Thus was not caught by any internal testing.
          thanks for the bug report and for the extra info (dumps).
          You'll need to wait until 10.3.15 to upgrade.

          wlad Vladislav Vaintroub added a comment - Well, this is a bug, which seems to happen only on quite old Windows versions now. Thus was not caught by any internal testing. thanks for the bug report and for the extra info (dumps). You'll need to wait until 10.3.15 to upgrade.
          BenYokoK Ben 136 added a comment -

          I can provide more information if need be, or run a version with a pdb file to get a more detailed crash report etc.

          BenYokoK Ben 136 added a comment - I can provide more information if need be, or run a version with a pdb file to get a more detailed crash report etc.
          BenYokoK Ben 136 added a comment -

          THANK YOU! Glad the bug report was helpful. Server 2008 is old, but still has active support from Microsoft, at least until 2020. I do need to upgrade it at some point.

          BenYokoK Ben 136 added a comment - THANK YOU! Glad the bug report was helpful. Server 2008 is old, but still has active support from Microsoft, at least until 2020. I do need to upgrade it at some point.

          Strictly speaking , Windows 2008 R2 support is not very active support, since 4 years it is in extended support, which is going to end soon.

          We do have PDBs, if you're interested, they can be downloaded from https://downloads.mariadb.org/mariadb/10.3.14/ (look for "debugsymbols" ZIPs)

          wlad Vladislav Vaintroub added a comment - Strictly speaking , Windows 2008 R2 support is not very active support, since 4 years it is in extended support, which is going to end soon. We do have PDBs, if you're interested, they can be downloaded from https://downloads.mariadb.org/mariadb/10.3.14/ (look for "debugsymbols" ZIPs)

          People

            wlad Vladislav Vaintroub
            BenYokoK Ben 136
            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.