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

mariadb-upgrade-service.exe gives FATAL ERROR on Windows

Details

    Description

      Hi,

      E:\wamp64\bin\mariadb\mariadb10.5.4\bin>mariadb-upgrade-service.exe --service=wampmariadb64
      FATAL ERROR: Not a valid MySQL service
      

      This also happens with MariaDB 10.4.13 or 10.3.23.
      This happens if service is created either with the Windows SC command or the (obsolete) mysqld.exe --install-manual command.

      sc create wampmariadb64 binpath="E:\wamp64\bin\mariadb\mariadb10.5.4\bin\mysqld.exe --defaults-file=E:\wamp64\bin\mariadb\mariadb10.5.4\.\my.ini wampmariadb64"
      

      E:/wamp64/bin/mariadb/mariadb10.5.4/bin/mysqld.exe --install-manual wampmariadb64 --defaults-file=E:\wamp64\bin\mariadb\mariadb10.5.4\my.ini
      

      Attachments

        Activity

          Instead of removing "no matter how the service was created" which will make the description ambiguous, I think it would be better to be positive and specify, for example "mariadb-upgrade-service.exe only supports services created by mysql_install_db.exe" or something like that.

          Otomatic Dominique Ottello added a comment - Instead of removing "no matter how the service was created" which will make the description ambiguous, I think it would be better to be positive and specify, for example "mariadb-upgrade-service.exe only supports services created by mysql_install_db.exe" or something like that.

          Unfortunately, it claims to support the services created with obsolete mysqld --install. I think I fixed the description so that there is no ambiguity.

          wlad Vladislav Vaintroub added a comment - Unfortunately, it claims to support the services created with obsolete mysqld --install. I think I fixed the description so that there is no ambiguity.

          > default-storage-engine=MYISAM, is that the WAMP default?
          It's been like this for more than sixteen years with MySQL before Wampserver also supports MariaDB.
          This doesn't prevent you from creating tables using another engine.
          Wampserver is primarily intended for beginners who want to learn about databases.
          This has never created any problem for "those who know".

          Otomatic Dominique Ottello added a comment - > default-storage-engine=MYISAM, is that the WAMP default? It's been like this for more than sixteen years with MySQL before Wampserver also supports MariaDB. This doesn't prevent you from creating tables using another engine. Wampserver is primarily intended for beginners who want to learn about databases. This has never created any problem for "those who know".

          it is just my opinion, but have a surprising effect for those beginners who learn about databases, to find out that ROLLBACK statement, as in SQL standard, does not work, and they should be using a non-standard extension ENGINE= , to make it work.
          On one hand, backward compatibility is commendable, yet given that Innodb has been default engine in MySQL for half of Wampserver existence, or longer, perhaps it could be a time to reconsider.

          wlad Vladislav Vaintroub added a comment - it is just my opinion, but have a surprising effect for those beginners who learn about databases, to find out that ROLLBACK statement, as in SQL standard, does not work, and they should be using a non-standard extension ENGINE= , to make it work. On one hand, backward compatibility is commendable, yet given that Innodb has been default engine in MySQL for half of Wampserver existence, or longer, perhaps it could be a time to reconsider.

          I fixed it in 10.1, and it will be merged up to 10.6, at some point.

          The problem with that my.ini file is that it uses service name instead of expected [mysqld], so the datadir was not determined, thus FATAL ERROR without much context.

          wlad Vladislav Vaintroub added a comment - I fixed it in 10.1, and it will be merged up to 10.6, at some point. The problem with that my.ini file is that it uses service name instead of expected [mysqld] , so the datadir was not determined, thus FATAL ERROR without much context.

          People

            wlad Vladislav Vaintroub
            Otomatic Dominique Ottello
            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.