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

Upgrades fail on Windows

Details

    Description

      Upgrading a new installation of 10.11.2 to 11.4.5 fails, and so does upgrading a new installation of 11.4.5 to 11.8.1. These are brand new installations in a pristine Windows 11 24H2 VM with nothing done before the upgrade attempts except to verify that the MariaDB service was running. In each case, the Upgrade Wizard quickly fails with message box "mysql_upgrade_service returned error for service MariaDB:" (the message really does stop there). Log files contain:

      10.11.2 to 11.4.5

      Executing "C:\Program Files\MariaDB 11.4\bin\mysqld.exe" "--defaults-file=C:\Program Files\MariaDB 10.11\data\my.ini" "--skip-networking" "--skip-grant-tables" "--enable-named-pipe" "--socket=mysql_upgrade_service_5472" "--skip-slave-start"
      		 
      Executing "C:\Program Files\MariaDB 11.4\bin\mysqladmin.exe" "--protocol=pipe" "--socket=mysql_upgrade_service_5472" "ping" "--no-beep"
      		 
      C:\Program Files\MariaDB 11.4\bin\mysqladmin.exe: connect to server at 'localhost' failed
      		 
      error: 'Can't open named pipe to host: .  pipe: mysql_upgrade_service_5472 (2)'
      		 
      Executing "C:\Program Files\MariaDB 11.4\bin\mysqladmin.exe" "--protocol=pipe" "--socket=mysql_upgrade_service_5472" "ping" "--no-beep"
      		 
      C:\Program Files\MariaDB 11.4\bin\mysqladmin.exe: connect to server at 'localhost' failed
      		 
      error: 'Can't open named pipe to host: .  pipe: mysql_upgrade_service_5472 (2)'
      		 
      Executing "C:\Program Files\MariaDB 11.4\bin\mysqladmin.exe" "--protocol=pipe" "--socket=mysql_upgrade_service_5472" "ping" "--no-beep"
      		 
      mysqld is alive
      		 
      Executing "C:\Program Files\MariaDB 11.4\bin\mysql_upgrade.exe" "--protocol=pipe" "--force" "--socket=mysql_upgrade_service_5472"
      		 
      Phase 1/8: Checking and upgrading mysql database
      		 
      FATAL ERROR: Upgrade failed

      11.4.5 to 11.8.1

      Executing "C:\Program Files\MariaDB 11.8\bin\mysqld.exe" "--defaults-file=C:\Program Files\MariaDB 11.4\data\my.ini" "--skip-networking" "--skip-grant-tables" "--enable-named-pipe" "--socket=mysql_upgrade_service_10216" "--skip-slave-start"
      		 
      Executing "C:\Program Files\MariaDB 11.8\bin\mysqladmin.exe" "--protocol=pipe" "--socket=mysql_upgrade_service_10216" "ping" "--no-beep"
      		 
      C:\Program Files\MariaDB 11.8\bin\mysqladmin.exe: connect to server at 'localhost' failed
      		 
      error: 'Can't open named pipe to host: .  pipe: mysql_upgrade_service_10216 (2)'
      		 
      Executing "C:\Program Files\MariaDB 11.8\bin\mysqladmin.exe" "--protocol=pipe" "--socket=mysql_upgrade_service_10216" "ping" "--no-beep"
      		 
      C:\Program Files\MariaDB 11.8\bin\mysqladmin.exe: connect to server at 'localhost' failed
      		 
      error: 'Can't open named pipe to host: .  pipe: mysql_upgrade_service_10216 (2)'
      		 
      Executing "C:\Program Files\MariaDB 11.8\bin\mysqladmin.exe" "--protocol=pipe" "--socket=mysql_upgrade_service_10216" "ping" "--no-beep"
      		 
      C:\Program Files\MariaDB 11.8\bin\mysqladmin.exe: connect to server at 'localhost' failed
      		 
      error: 'Can't open named pipe to host: .  pipe: mysql_upgrade_service_10216 (2)'
      		 
      Executing "C:\Program Files\MariaDB 11.8\bin\mysqladmin.exe" "--protocol=pipe" "--socket=mysql_upgrade_service_10216" "ping" "--no-beep"
      		 
      mysqld is alive
      		 
      Executing "C:\Program Files\MariaDB 11.8\bin\mysql_upgrade.exe" "--protocol=pipe" "--force" "--socket=mysql_upgrade_service_10216"
      		 
      Phase 1/8: Checking and upgrading mysql database
      		 
      FATAL ERROR: Upgrade failed

      The above is the simplified version of the bug demonstrating that upgrades fail even from a default installation with no user actions performed between installation and upgrade attempt. I actually encountered this trying to upgrade my real, deployed installation of 10.11.2, and there's more information in the reddit thread I created for it, where I noted that upgrading 10.11.2 to 11.0.1 was possible, but all later versions failed.

      https://www.reddit.com/r/mariadb/comments/1iqd4ii/windows_11_cannot_upgrade_10112_database_beyond/

      Attachments

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. CONC-760 valid named pipe connection is closed, if reconnect is set

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          relates to

          Task - A task that needs to be done. MDEV-19430 Test upgrade on Windows, via mysql_upgrade_service

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MDEV-31637 Impossible to upgrade MariaDB (either 10.X / 11.X) on Windows.

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-36127 Add mtr tests for mariadb-upgrade-service.exe

          • Major - Major loss of function.
          • Closed
          links to

          Web Link Zulip thread

          Activity

            Ascending order - Click to sort in descending order
            wlad Vladislav Vaintroub added a comment - - edited

            Unfortunately, all fresh releases are affected, i.e cross-version upgrade with the underlying mariadb-upgrade-service.exe is not possible. The prior-to-that versions worked (except the ones affected by MDEV-30639, this was a similar glitch 2 years ago)

            All due to CONC-760

            wlad Vladislav Vaintroub added a comment - - edited Unfortunately, all fresh releases are affected, i.e cross-version upgrade with the underlying mariadb-upgrade-service.exe is not possible. The prior-to-that versions worked (except the ones affected by MDEV-30639 , this was a similar glitch 2 years ago) All due to CONC-760
            wlad Vladislav Vaintroub added a comment -

            A workaround, which will work almost everywhere would be to do something like

            C:\> sc.exe config MariaDB binPath= "\"C:\Program Files\MariaDB 11.7\bin\mysqld.exe\" \"--defaults-file=C:\Program Files\MariaDB 10.6\data\my.ini\" \"MariaDB\""

            to fix Windows service definition in cmd.exe (elevated)
            then maybe run mysql_upgrade manually. You can adapt that to your case . in the example, 11.7 is the destination version, 11.6 is the source version, the last argument in binPath. "MariaDB" has to match service name

            Dunno how to fix that in powershell, escaping rules are tricky

            wlad Vladislav Vaintroub added a comment - A workaround, which will work almost everywhere would be to do something like C:\> sc.exe config MariaDB binPath= "\"C:\Program Files\MariaDB 11.7\bin\mysqld.exe\" \"--defaults-file=C:\Program Files\MariaDB 10.6\data\my.ini\" \"MariaDB\"" to fix Windows service definition in cmd.exe (elevated) then maybe run mysql_upgrade manually. You can adapt that to your case . in the example, 11.7 is the destination version, 11.6 is the source version, the last argument in binPath. "MariaDB" has to match service name Dunno how to fix that in powershell, escaping rules are tricky
            wlad Vladislav Vaintroub added a comment -

            CONC-760 fixed, MTR tests added in MDEV-36127.
            Closing.

            wlad Vladislav Vaintroub added a comment - CONC-760 fixed, MTR tests added in MDEV-36127 . Closing.

            People

              wlad Vladislav Vaintroub
              deviltrombone Dev Trom
              Votes:
              2 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.