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

debian upgrade shouldn't start previously stopped services

Details

    Description

      When doing a debian/ubuntu upgrade, if you have mariadb installed and stopped as a service, the process of doing an `apt-get upgrade` shouldn't start the mariadb service.

      This applies both to systemd and sysv.

      Additionally for systemd, systemd multiinstances e.g.`mariadb@xyz`, those that are started before the upgrade, should be stopped, and restarted after the upgrade.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-17739 mariadb-server-10.1: Updates not restarting mariadb@xx services

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23050 MariaDB Server failure on Proxmox (with Ubuntu 20.04 and Systemd)

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23755 safety for upgrades (innodb) and packaging

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

          Web Link debian systemd maintainers non-answer

          Web Link debian-policy: maintainer scripts

          Web Link dh_installsystemd source code

          Web Link Maintainer Scripts graphs on script ordering

          Web Link SO - mysql equivilant problem

          Activity

            No workflow transitions have been executed yet.

            People

              Unassigned Unassigned
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.