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

mariadb-server-10.1: Updates not restarting mariadb@xx services

Details

    Description

      Dear Maintainer,

      We had installed and running Multi-instance version of mariadb.

      Today when i fire `apt-get dist-upgrade` command mariadb update failed.

      The following packages will be upgraded:
        mariadb-server-10.1
      1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
      Need to get 0 B/7230 kB of archives.
      After this operation, 1024 B of additional disk space will be used.
      Do you want to continue? [Y/n] y
      Preconfiguring packages ...
      (Reading database ... 156043 files and directories currently installed.)
      Preparing to unpack .../mariadb-server-10.1_1%3a10.1.37+maria-1~bionic_amd64.deb ...
      Failed to stop mysql.service: Unit mysql.service not loaded.
      invoke-rc.d: initscript mysql, action "stop" failed.
      dpkg: warning: old mariadb-server-10.1 package pre-removal script subprocess returned error exit status 1
      dpkg: trying script from the new package instead ...
      Failed to stop mysql.service: Unit mysql.service not loaded.
      invoke-rc.d: initscript mysql, action "stop" failed.
      dpkg: error processing archive /var/cache/apt/archives/mariadb-server-10.1_1%3a10.1.37+maria-1~bionic_amd64.deb (--unpack):
       new mariadb-server-10.1 package pre-removal script subprocess returned error exit status 1
      Failed to stop mysql.service: Unit mysql.service not loaded.
      invoke-rc.d: initscript mysql, action "stop" failed.
      Errors were encountered while processing:
       /var/cache/apt/archives/mariadb-server-10.1_1%3a10.1.37+maria-1~bionic_amd64.deb
      E: Sub-process /usr/bin/dpkg returned an error code (1)
      

      When using MariaDB multiple instances the upgrade process shows errors stopping/starting mysql and the servers are not restarted. Would be great if the upgrade scripts could detect running mariadb@xxx services (`systemctl | grep mariadb`??) and stop/restart them, instead of assuming a single mariadb service.

      Attachments

        Issue Links

          Activity

            ShahMitesh Mitesh Shah created issue -
            elenst Elena Stepanova made changes -
            Field Original Value New Value
            Priority Critical [ 2 ] Major [ 3 ]
            elenst Elena Stepanova made changes -
            Assignee Jonathan Oxer [ jonoxer ]
            elenst Elena Stepanova made changes -
            Fix Version/s 10.3 [ 22126 ]
            elenst Elena Stepanova made changes -
            Component/s Platform Debian [ 10136 ]
            elenst Elena Stepanova made changes -
            Labels MariaDB-server
            serg Sergei Golubchik made changes -
            Fix Version/s 10.4 [ 22408 ]
            faust Faustin Lammler made changes -
            Labels systemd
            serg Sergei Golubchik made changes -
            Assignee Jonathan Oxer [ jonoxer ] Axel Schwenke [ axel ]
            axel Axel Schwenke made changes -
            Assignee Axel Schwenke [ axel ] Daniel Black [ danblack ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 90730 ] MariaDB v4 [ 141018 ]
            julien.fritsch Julien Fritsch made changes -
            Fix Version/s 10.3 [ 22126 ]
            danblack Daniel Black made changes -
            Assignee Daniel Black [ danblack ] Tuukka Pasanen [ JIRAUSER49166 ]
            danblack Daniel Black made changes -
            illuusio Tuukka Pasanen made changes -
            Assignee Tuukka Pasanen [ JIRAUSER49166 ]

            People

              Unassigned Unassigned
              ShahMitesh Mitesh Shah
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.