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

Distro's mysql server does not get removed upon installation of MariaDB and keeps running on SLES11

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • N/A
    • 10.1(EOL)
    • Packaging
    • None
    • 10.1.14

    Description

      On SLES 11 mysql (5.5) is the server provided by default.

      rpm -qa | grep -iE 'maria|mysql|galera|percona'
      mysql-5.5.47-0.17.1
      mysql-client-5.5.47-0.17.1
      

      After installation of MariaDB , the client gets removed, but the server stays and keeps running:

      rpm -qa | grep -iE 'maria|mysql|galera|percona'
      mysql-5.5.47-0.17.1
      MariaDB-client-10.1.14-1
      MariaDB-common-10.1.14-1
      galera-25.3.15-1.sles11.sle11
      MariaDB-server-10.1.14-1
      

      mysql -uroot -e 'select @@version, @@version_comment'
      +-----------+--------------------+
      | @@version | @@version_comment  |
      +-----------+--------------------+
      | 5.5.47    | SUSE MySQL package |
      +-----------+--------------------+
      

      It also says upon installation, might be related:

      Additional rpm output:
      insserv: Service network is missed in the runlevels 4 to use service mysql
      mysql                     0:off  1:off  2:on   3:on   4:on   5:on   6:off
       
       
      There are some running programs that use files deleted by recent upgrade. You may wish to restart some of them. Run 'zypper ps' to list these programs.
      

      Attachments

        Issue Links

          Activity

            People

              serg Sergei Golubchik
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.