2.5 Installing MySQL on Linux

Linux supports a number of different solutions for installing MySQL. We recommend that you use one of the distributions from Oracle, for which several methods for installation are available:

Linux Installation Methods and Information

Type Setup Method Additional Information

Apt

Enable the MySQL Apt *note Documentation: linux-installation-apt-repo. repository
(https://dev.mysql.com/downloads/repo/apt/)

Yum

Enable the MySQL Yum *note Documentation: linux-installation-yum-repo. repository
(https://dev.mysql.com/downloads/repo/yum/)

Zypper

Enable the MySQL *note Documentation: linux-installation-sles-repo. SLES repository
(https://dev.mysql.com/downloads/repo/suse/)

RPM

Download *note Documentation: linux-installation-rpm. (https://dev.mysql.com/downloads/mysql/) a specific package

DEB

Download *note Documentation: linux-installation-debian. (https://dev.mysql.com/downloads/mysql/) a specific package

Generic

Download *note Documentation: binary-installation. (https://dev.mysql.com/downloads/mysql/) a generic package

Source

Compile from source *note Documentation: source-installation. (https://dev.mysql.com/downloads/mysql/)

Docker

Use the Oracle *note Documentation: linux-installation-docker. Container Registry
(https://container-registry.oracle.com/). You can also use My Oracle Support (https://support.oracle.com/) for the MySQL Enterprise Edition.

Oracle Unbreakable Linux Network

Use ULN channels *note Documentation: uln-installation.

As an alternative, you can use the package manager on your system to automatically download and install MySQL with packages from the native software repositories of your Linux distribution. These native packages are often several versions behind the currently available release. You also normally cannot install development milestone releases (DMRs), as these are not usually made available in the native repositories. For more information on using the native package installers, see *note linux-installation-native::.

Note:

For many Linux installations, you may want to set up MySQL to be started automatically when your machine starts. Many of the native package installations perform this operation for you, but for source, binary and RPM solutions you may need to set this up separately. The required script, note 'mysql.server': mysql-server, can be found in the 'support-files' directory under the MySQL installation directory or in a MySQL source tree. You can install it as '/etc/init.d/mysql' for automatic MySQL startup and shutdown. See note mysql-server::.

 File: manual.info.tmp, Node: linux-installation-yum-repo, Next: replace-third-party-yum, Prev: linux-installation, Up: linux-installation

2.5.1 Installing MySQL on Linux Using the MySQL Yum Repository

The MySQL Yum repository (https://dev.mysql.com/downloads/repo/yum/) for Oracle Linux, Red Hat Enterprise Linux and CentOS provides RPM packages for installing the MySQL server, client, MySQL Workbench, MySQL Utilities, MySQL Router, MySQL Shell, Connector/ODBC, Connector/Python and so on (not all packages are available for all the distributions; see *note yum-install-components:: for details).

Before You Start

As a popular, open-source software, MySQL, in its original or re-packaged form, is widely installed on many systems from various sources, including different software download sites, software repositories, and so on. The following instructions assume that MySQL is not already installed on your system using a third-party-distributed RPM package; if that is not the case, follow the instructions given in note updating-yum-repo:: or note replace-third-party-yum::.

Steps for a Fresh Installation of MySQL

Follow the steps below to install the latest GA version of MySQL with the MySQL Yum repository:

  1. Adding the MySQL Yum Repository

    First, add the MySQL Yum repository to your system's repository list. This is a one-time operation, which can be performed by installing an RPM provided by MySQL. Follow these steps:

    1. Go to the Download MySQL Yum Repository page (https://dev.mysql.com/downloads/repo/yum/ (https://dev.mysql.com/downloads/repo/yum/)) in the MySQL Developer Zone.

    2. Select and download the release package for your platform.

    3. Install the downloaded release package with the following command, replacing PLATFORM-AND-VERSION-SPECIFIC-PACKAGE-NAME with the name of the downloaded RPM package:

         $> sudo yum localinstall PLATFORM-AND-VERSION-SPECIFIC-PACKAGE-NAME.rpm

      For an EL6-based system, the command is in the form of:

         $> sudo yum localinstall mysql57-community-release-el6-{VERSION-NUMBER}.noarch.rpm

      For an EL7-based system:

         $> sudo yum localinstall mysql57-community-release-el7-{VERSION-NUMBER}.noarch.rpm

      For an EL8-based system:

         $> sudo yum localinstall mysql57-community-release-el8-{VERSION-NUMBER}.noarch.rpm

      For Fedora:

      MySQL 5.7 does not support Fedora; support was removed in MySQL 5.7.30. For details, see the MySQL Product Support EOL Announcements (https://www.mysql.com/support/eol-notice.html).

      The installation command adds the MySQL Yum repository to your system's repository list and downloads the GnuPG key to check the integrity of the software packages. See *note checking-gpg-signature:: for details on GnuPG key checking.

      You can check that the MySQL Yum repository has been successfully added by the following command:

         $> yum repolist enabled | grep "mysql.*-community.*"

    Note:

    Once the MySQL Yum repository is enabled on your system, any system-wide update by the 'yum update' command upgrades MySQL packages on your system and replaces any native third-party packages, if Yum finds replacements for them in the MySQL Yum repository; see note updating-yum-repo:: and, for a discussion on some possible effects of that on your system, see note updating-yum-repo-client-lib::.

  2. Selecting a Release Series

    When using the MySQL Yum repository, the latest GA series (currently MySQL 5.7) is selected for installation by default. If this is what you want, you can skip to the next step, *note yum-repo-installing-mysql::.

    Within the MySQL Yum repository, different release series of the MySQL Community Server are hosted in different subrepositories. The subrepository for the latest GA series (currently MySQL 5.7) is enabled by default, and the subrepositories for all other series (for example, the MySQL 5.6 series) are disabled by default. Use this command to see all the subrepositories in the MySQL Yum repository, and see which of them are enabled or disabled:

      $> yum repolist all | grep mysql

    To install the latest release from the latest GA series, no configuration is needed. To install the latest release from a specific series other than the latest GA series, disable the subrepository for the latest GA series and enable the subrepository for the specific series before running the installation command. If your platform supports 'yum-config-manager', you can do that by issuing these commands, which disable the subrepository for the 5.7 series and enable the one for the 5.6 series:

      $> sudo yum-config-manager --disable mysql57-community
  $> sudo yum-config-manager --enable mysql56-community

    For Fedora platforms:

      $> sudo dnf config-manager --disable mysql57-community
  $> sudo dnf config-manager --enable mysql56-community

    Besides using 'yum-config-manager' or the 'dnf config-manager' command, you can also select a release series by editing manually the '/etc/yum.repos.d/mysql-community.repo' file. This is a typical entry for a release series' subrepository in the file:

      [mysql57-community]
  name=MySQL 5.7 Community Server
  baseurl=http://repo.mysql.com/yum/mysql-5.7-community/el/6/$basearch/
  enabled=1
  gpgcheck=1
  gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql

    Find the entry for the subrepository you want to configure, and edit the 'enabled' option. Specify 'enabled=0' to disable a subrepository, or 'enabled=1' to enable a subrepository. For example, to install MySQL 5.6, make sure you have 'enabled=0' for the above subrepository entry for MySQL 5.7, and have 'enabled=1' for the entry for the 5.6 series:

      # Enable to use MySQL 5.6
  [mysql56-community]
  name=MySQL 5.6 Community Server
  baseurl=http://repo.mysql.com/yum/mysql-5.6-community/el/6/$basearch/
  enabled=1
  gpgcheck=1
  gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql

    You should only enable subrepository for one release series at any time. When subrepositories for more than one release series are enabled, the latest series is used by Yum.

    Verify that the correct subrepositories have been enabled and disabled by running the following command and checking its output:

      $> yum repolist enabled | grep mysql

  3. Disabling the Default MySQL Module

    (EL8 systems only) EL8-based systems such as RHEL8 and Oracle Linux 8 include a MySQL module that is enabled by default. Unless this module is disabled, it masks packages provided by MySQL repositories. To disable the included module and make the MySQL repository packages visible, use the following command (for dnf-enabled systems, replace 'yum' in the command with 'dnf'):

      $> sudo yum module disable mysql

  4. Installing MySQL

    Install MySQL by the following command:

      $> sudo yum install mysql-community-server

    This installs the package for MySQL server ('mysql-community-server') and also packages for the components required to run the server, including packages for the client ('mysql-community-client'), the common error messages and character sets for client and server ('mysql-community-common'), and the shared client libraries ('mysql-community-libs').

  5. Starting the MySQL Server

    Start the MySQL server with the following command:

      $> sudo service mysqld start
  Starting mysqld:[ OK ]

    You can check the status of the MySQL server with the following command:

      $> sudo service mysqld status
  mysqld (pid 3066) is running.

At the initial start up of the server, the following happens, given that the data directory of the server is empty:

For more information on the postinstallation procedures, see *note postinstallation::.

Note:

Compatibility Information for EL7-based platforms: The following RPM packages from the native software repositories of the platforms are incompatible with the package from the MySQL Yum repository that installs the MySQL server. Once you have installed MySQL using the MySQL Yum repository, you cannot install these packages (and vice versa).

Installing Additional MySQL Products and Components with Yum

You can use Yum to install and manage individual components of MySQL. Some of these components are hosted in sub-repositories of the MySQL Yum repository: for example, the MySQL Connectors are to be found in the MySQL Connectors Community sub-repository, and the MySQL Workbench in MySQL Tools Community. You can use the following command to list the packages for all the MySQL components available for your platform from the MySQL Yum repository:

 $> sudo yum --disablerepo=\* --enablerepo='mysql*-community*' list available

Install any packages of your choice with the following command, replacing PACKAGE-NAME with name of the package:

 $> sudo yum install PACKAGE-NAME

For example, to install MySQL Workbench on Fedora:

 $> sudo dnf install mysql-workbench-community

To install the shared client libraries:

 $> sudo yum install mysql-community-libs

Updating MySQL with Yum

Besides installation, you can also perform updates for MySQL products and components using the MySQL Yum repository. See *note updating-yum-repo:: for details.

 File: manual.info.tmp, Node: replace-third-party-yum, Next: linux-installation-apt-repo, Prev: linux-installation-yum-repo, Up: linux-installation

2.5.2 Replacing a Third-Party Distribution of MySQL Using the MySQL Yum Repository

For supported Yum-based platforms (see *note linux-installation-yum-repo::, for a list), you can replace a third-party distribution of MySQL with the latest GA release (from the MySQL 5.7 series currently)

from the MySQL Yum repository. According to how your third-party distribution of MySQL was installed, there are different steps to follow:

Replacing a Native Third-Party Distribution of MySQL

If you have installed a third-party distribution of MySQL from a native software repository (that is, a software repository provided by your own Linux distribution), follow these steps:

  1. Backing Up Your Database

    To avoid loss of data, always back up your database before trying to replace your MySQL installation using the MySQL Yum repository. See *note backup-and-recovery::, on how to back up your database.

  2. Adding the MySQL Yum Repository

    Add the MySQL Yum repository to your system's repository list by following the instructions given in *note yum-repo-setup::.

  3. Replacing the Native Third-Party Distribution by a Yum Update or a DNF Upgrade

    By design, the MySQL Yum repository replaces your native third-party MySQL with the latest GA release (from the MySQL 5.7 series currently) from the MySQL Yum repository when you perform a 'yum update' command on the system, or a 'yum update mysql-server'.

After updating MySQL using the Yum repository, applications compiled with older versions of the shared client libraries should continue to work. However, if you want to recompile applications and dynamically link them with the updated libraries, see *note updating-yum-repo-client-lib::, for some special considerations.

Replacing a Nonnative Third-Party Distribution of MySQL

If you have installed a third-party distribution of MySQL from a nonnative software repository (that is, a software repository not provided by your own Linux distribution), follow these steps:

  1. Backing Up Your Database

    To avoid loss of data, always back up your database before trying to replace your MySQL installation using the MySQL Yum repository. See *note backup-and-recovery::, on how to back up your database.

  2. Stopping Yum from Receiving MySQL Packages from Third-Party, Nonnative Repositories

    Before you can use the MySQL Yum repository for installing MySQL, you must stop your system from receiving MySQL packages from any third-party, nonnative Yum repositories.

    For example, if you have installed MariaDB using their own software repository, get a list of the installed MariaDB packages using the following command:

      $> yum list installed mariadb\*
  MariaDB-common.i686                      10.0.4-1                       @mariadb
  MariaDB-compat.i686                      10.0.4-1                       @mariadb
  MariaDB-server.i686                      10.0.4-1                       @mariadb

    From the command output, we can identify the installed packages ('MariaDB-common', 'MariaDB-compat', and 'MariaDB-server') and the source of them (a nonnative software repository named 'mariadb').

    As another example, if you have installed Percona using their own software repository, get a list of the installed Percona packages using the following command:

      $> yum list installed Percona\*
  Percona-Server-client-55.i686     5.5.39-rel36.0.el6          @percona-release-i386
  Percona-Server-server-55.i686     5.5.39-rel36.0.el6          @percona-release-i386
  Percona-Server-shared-55.i686     5.5.39-rel36.0.el6          @percona-release-i386
  percona-release.noarch            0.1-3                       @/percona-release-0.1-3.noarch

    From the command output, we can identify the installed packages ('Percona-Server-client', 'Percona-Server-server', 'Percona-Server-shared', and 'percona-release.noarch') and the source of them (a nonnative software repository named 'percona-release').

    If you are not sure which third-party MySQL fork you have installed, this command should reveal it and list the RPM packages installed for it, as well as the third-party repository that supplies the packages:

      $> yum --disablerepo=\* provides mysql\*

    The next step is to stop Yum from receiving packages from the nonnative repository. If the 'yum-config-manager' utility is supported on your platform, you can, for example, use this command for stopping delivery from MariaDB:

      $> sudo yum-config-manager --disable mariadb

    Use this command for stopping delivery from Percona:

      $> sudo yum-config-manager --disable percona-release

    You can perform the same task by removing the entry for the software repository existing in one of the repository files under the '/etc/yum.repos.d/' directory. This is how the entry typically looks for MariaDB:

      [mariadb] name = MariaDB
   baseurl = [BASE URL FOR REPOSITORY]
   gpgkey = [URL FOR GPG KEY]
   gpgcheck =1

    The entry is usually found in the file '/etc/yum.repos.d/MariaDB.repo' for MariaDB--delete the file, or remove entry from it (or from the file in which you find the entry).

    Note:

    This step is not necessary for an installation that was configured with a Yum repository release package (like Percona) if you are going to remove the release package ('percona-release.noarch' for Percona), as shown in the uninstall command for Percona in Step 3 below.

  3. Uninstalling the Nonnative Third-Party MySQL Distribution of MySQL

    The nonnative third-party MySQL distribution must first be uninstalled before you can use the MySQL Yum repository to install MySQL. For the MariaDB packages found in Step 2 above, uninstall them with the following command:

      $> sudo yum remove MariaDB-common MariaDB-compat MariaDB-server

    For the Percona packages we found in Step 2 above:

      $> sudo yum remove Percona-Server-client-55 Percona-Server-server-55 \
    Percona-Server-shared-55.i686 percona-release

  4. Installing MySQL with the MySQL Yum Repository

    Then, install MySQL with the MySQL Yum repository by following the instructions given in *note linux-installation-yum-repo::: .

    Important:

    If you have chosen to replace your third-party MySQL distribution with a newer version of MySQL from the MySQL Yum repository, remember to run note 'mysql_upgrade': mysql-upgrade. after the server starts, to check and possibly resolve any incompatibilities between the old data and the upgraded software. note 'mysql_upgrade': mysql-upgrade. also performs other functions; see *note mysql-upgrade:: for details.

    For EL7-based platforms: See *note yum-install-compatibility-el7::.

 File: manual.info.tmp, Node: linux-installation-apt-repo, Next: linux-installation-sles-repo, Prev: replace-third-party-yum, Up: linux-installation

2.5.3 Installing MySQL on Linux Using the MySQL APT Repository

The MySQL APT repository provides 'deb' packages for installing and managing the MySQL server, client, and other components on the current Debian and Ubuntu releases.

Instructions for using the MySQL APT Repository are available in A Quick Guide to Using the MySQL APT Repository (https://dev.mysql.com/doc/mysql-apt-repo-quick-guide/en/).

 File: manual.info.tmp, Node: linux-installation-sles-repo, Next: linux-installation-rpm, Prev: linux-installation-apt-repo, Up: linux-installation

2.5.4 Installing MySQL on Linux Using the MySQL SLES Repository

The MySQL SLES repository provides RPM packages for installing and managing the MySQL server, client, and other components on SUSE Enterprise Linux Server.

Instructions for using the MySQL SLES repository are available in A Quick Guide to Using the MySQL SLES Repository (https://dev.mysql.com/doc/mysql-sles-repo-quick-guide/en/).

 File: manual.info.tmp, Node: linux-installation-rpm, Next: linux-installation-debian, Prev: linux-installation-sles-repo, Up: linux-installation

2.5.5 Installing MySQL on Linux Using RPM Packages from Oracle

The recommended way to install MySQL on RPM-based Linux distributions is by using the RPM packages provided by Oracle. There are two sources for obtaining them, for the Community Edition of MySQL:

Note:

RPM distributions of MySQL are also provided by other vendors. Be aware that they may differ from those built by Oracle in features, capabilities, and conventions (including communication setup), and that the installation instructions in this manual do not necessarily apply to them. The vendor's instructions should be consulted instead.

If you have such a third-party distribution of MySQL running on your system and now want to migrate to Oracle's distribution using the RPM packages downloaded from the MySQL Developer Zone, see note linux-installing-rpm-compat:: below. The preferred method of migration, however, is to use the note MySQL Yum repository: linux-installation-yum-repo. or *note MySQL SLES repository: linux-installation-sles-repo.

RPM packages for MySQL are listed in the following tables:

RPM Packages for MySQL Community Edition

Package Name Summary

'mysql-community-server' Database server and related tools

'mysql-community-client' MySQL client applications and tools

'mysql-community-common' Common files for server and client libraries

'mysql-community-devel' Development header files and libraries for MySQL database client applications

'mysql-community-libs' Shared libraries for MySQL database client applications

'mysql-community-libs-compat'Shared compatibility libraries for previous MySQL installations

'mysql-community-embedded'MySQL embedded library

'mysql-community-embedded-devel'Development header files and libraries for MySQL as an embeddable library

'mysql-community-test' Test suite for the MySQL server

RPM Packages for the MySQL Enterprise Edition

Package Name Summary

'mysql-commercial-server' Database server and related tools

'mysql-commercial-client' MySQL client applications and tools

'mysql-commercial-common' Common files for server and client libraries

'mysql-commercial-devel' Development header files and libraries for MySQL database client applications

'mysql-commercial-libs' Shared libraries for MySQL database client applications

'mysql-commercial-libs-compat'Shared compatibility libraries for previous MySQL installations

'mysql-commercial-embedded'MySQL embedded library

'mysql-commercial-embedded-devel'Development header files and libraries for MySQL as an embeddable library

'mysql-commercial-test' Test suite for the MySQL server

The full names for the RPMs have the following syntax:

 PACKAGENAME-VERSION-DISTRIBUTION-ARCH.rpm

The DISTRIBUTION and ARCH values indicate the Linux distribution and the processor type for which the package was built. See the table below for lists of the distribution identifiers:

MySQL Linux RPM Package Distribution Identifiers

distribution Intended Use Value

el{VERSION} EL6 (8.0), EL7, EL8, and EL9-based platforms (for where {VERSION} example, the corresponding versions of Oracle Linux, is the major Red Hat Enterprise Linux, and CentOS) Enterprise Linux
version, such as 'el8'

'sles12' SUSE Linux Enterprise Server 12

To see all files in an RPM package (for example, 'mysql-community-server'), use the following command:

 $> rpm -qpl mysql-community-server-VERSION-DISTRIBUTION-ARCH.rpm

The discussion in the rest of this section applies only to an installation process using the RPM packages directly downloaded from Oracle, instead of through a MySQL repository.

Dependency relationships exist among some of the packages. If you plan to install many of the packages, you may wish to download the RPM bundle 'tar' file instead, which contains all the RPM packages listed above, so that you need not download them separately.

In most cases, you need to install the 'mysql-community-server', 'mysql-community-client', 'mysql-community-libs', 'mysql-community-common', and 'mysql-community-libs-compat' packages to get a functional, standard MySQL installation. To perform such a standard, basic installation, go to the folder that contains all those packages (and, preferably, no other RPM packages with similar names), and issue the following command for platforms other than Red Hat Enterprise Linux/Oracle Linux/CentOS:

 $> sudo yum install mysql-community-{server,client,common,libs}-*

Replace 'yum' with 'zypper' for SLES.

For Red Hat Enterprise Linux/Oracle Linux/CentOS systems:

 $> sudo yum install mysql-community-{server,client,common,libs}-* mysql-5.*­

While it is much preferable to use a high-level package management tool like 'yum' to install the packages, users who prefer direct 'rpm' commands can replace the 'yum install' command with the 'rpm -Uvh' command; however, using 'rpm -Uvh' instead makes the installation process more prone to failure, due to potential dependency issues the installation process might run into.

To install only the client programs, you can skip 'mysql-community-server' in your list of packages to install; issue the following command for platforms other than Red Hat Enterprise Linux/Oracle Linux/CentOS:

 $> sudo yum install mysql-community-{client,common,libs}-*

Replace 'yum' with 'zypper' for SLES.

For Red Hat Enterprise Linux/Oracle Linux/CentOS systems:

 $> sudo yum install mysql-community-{client,common,libs}-* mysql-5.*

A standard installation of MySQL using the RPM packages result in files and resources created under the system directories, shown in the following table.

MySQL Installation Layout for Linux RPM Packages from the MySQL Developer Zone

Files or Resources Location

Client programs and scripts '/usr/bin'

*note 'mysqld': mysqld. server '/usr/sbin'

Configuration file '/etc/my.cnf'

Data directory '/var/lib/mysql'

Error log file
For RHEL, Oracle Linux, CentOS or Fedora platforms: '/var/log/mysqld.log'

                                     For SLES:
                                     '/var/log/mysql/mysqld.log'

Value of 'secure_file_priv' '/var/lib/mysql-files'

System V init script
For RHEL, Oracle Linux, CentOS or Fedora platforms: '/etc/init.d/mysqld'

                                     For SLES: '/etc/init.d/mysql'

Systemd service
For RHEL, Oracle Linux, CentOS or Fedora platforms: 'mysqld'

                                     For SLES: 'mysql'

Pid file ' /var/run/mysql/mysqld.pid'

Socket '/var/lib/mysql/mysql.sock'

Keyring directory '/var/lib/mysql-keyring'

Unix manual pages '/usr/share/man'

Include (header) files '/usr/include/mysql'

Libraries '/usr/lib/mysql'

Miscellaneous support files (for '/usr/share/mysql' example, error messages, and character set files)

The installation also creates a user named 'mysql' and a group named 'mysql' on the system.

Notes:

MySQL is not automatically started at the end of the installation process. For Red Hat Enterprise Linux, Oracle Linux, CentOS, and Fedora systems, use the following command to start MySQL:

 $> sudo service mysqld start

For SLES systems, the command is the same, but the service name is different:

 $> sudo service mysql start

If the operating system is systemd enabled, standard 'service' commands such as 'stop', 'start', 'status' and 'restart' should be used to manage the MySQL server service. The 'mysqld' service is enabled by default, and it starts at system reboot. Notice that certain things might work differently on systemd platforms: for example, changing the location of the data directory might cause issues. See *note using-systemd:: for additional information.

During an upgrade installation using RPM and DEB packages, if the MySQL server is running when the upgrade occurs then the MySQL server is stopped, the upgrade occurs, and the MySQL server is restarted. One exception: if the edition also changes during an upgrade (such as community to commercial, or vice-versa), then MySQL server is not restarted.

At the initial start up of the server, the following happens, given that the data directory of the server is empty:

Note:

*note 'validate_password': validate-password. is installed by default. The default password policy implemented by 'validate_password' requires that passwords contain at least one uppercase letter, one lowercase letter, one digit, and one special character, and that the total password length is at least 8 characters.

If something goes wrong during installation, you might find debug information in the error log file '/var/log/mysqld.log'.

For some Linux distributions, it might be necessary to increase the limit on number of file descriptors available to note 'mysqld': mysqld. See note not-enough-file-handles::

Compatibility with RPM Packages from Other Vendors

If you have installed packages for MySQL from your Linux distribution's local software repository, it is much preferable to install the new, directly-downloaded packages from Oracle using the package management system of your platform ('yum', 'dnf', or 'zypper'), as described above. The command replaces old packages with new ones to ensure compatibility of old applications with the new installation; for example, the old 'mysql-libs' package is replaced with the 'mysql-community-libs-compat' package, which provides a replacement-compatible client library for applications that were using your older MySQL installation. If there was an older version of 'mysql-community-libs-compat' on the system, it also gets replaced.

If you have installed third-party packages for MySQL that are NOT from your Linux distribution's local software repository (for example, packages directly downloaded from a vendor other than Oracle), you should uninstall all those packages before installing the new, directly-downloaded packages from Oracle. This is because conflicts may arise between those vendor's RPM packages and Oracle's: for example, a vendor's convention about which files belong with the server and which belong with the client library may differ from that used for Oracle packages. Attempts to install an Oracle RPM may then result in messages saying that files in the RPM to be installed conflict with files from an installed package.

Installing Client Libraries from Multiple MySQL Versions

It is possible to install multiple client library versions, such as for the case that you want to maintain compatibility with older applications linked against previous libraries. To install an older client library, use the '--oldpackage' option with 'rpm'. For example, to install 'mysql-community-libs-5.5' on an EL6 system that has 'libmysqlclient.20' from MySQL 5.7, use a command like this:

 $> rpm --oldpackage -ivh mysql-community-libs-5.5.50-2.el6.x86_64.rpm

Debug Package

A special variant of MySQL Server compiled with the note debug package: dbug-package. has been included in the server RPM packages. It performs debugging and memory allocation checks and produces a trace file when the server is running. To use that debug version, start MySQL with '/usr/sbin/mysqld-debug', instead of starting it as a service or with '/usr/sbin/mysqld'. See note dbug-package:: for the debug options you can use.

Note:

The default plugin directory for debug builds changed from '/usr/lib64/mysql/plugin' to '/usr/lib64/mysql/plugin/debug' in 5.7.21. Previously, it was necessary to change 'plugin_dir' to '/usr/lib64/mysql/plugin/debug' for debug builds.

Rebuilding RPMs from source SRPMs

Source code SRPM packages for MySQL are available for download. They can be used as-is to rebuild the MySQL RPMs with the standard 'rpmbuild' tool chain.

'root' passwords for pre-GA releases

For MySQL 5.7.4 and 5.7.5, the initial random 'root' password is written to the '.mysql_secret' file in the directory named by the 'HOME' environment variable. When trying to access the file, bear in mind that depending on operating system, using a command such as 'sudo' may cause the value of 'HOME' to refer to the home directory of the 'root' system user

. '.mysql_secret' is created with mode 600 to be accessible only to the system user for whom it is created. Before MySQL 5.7.4, the accounts (including 'root') created in the MySQL grant tables for an RPM installation initially have no passwords; after starting the server, you should assign passwords to them using the instructions in *note postinstallation::."

 File: manual.info.tmp, Node: linux-installation-debian, Next: linux-installation-docker, Prev: linux-installation-rpm, Up: linux-installation

2.5.6 Installing MySQL on Linux Using Debian Packages from Oracle

Oracle provides Debian packages for installing MySQL on Debian or Debian-like Linux systems. The packages are available through two different channels:

Note:

Debian distributions of MySQL are also provided by other vendors. Be aware that they may differ from those built by Oracle in features, capabilities, and conventions (including communication setup), and that the instructions in this manual do not necessarily apply to installing them. The vendor's instructions should be consulted instead.

 File: manual.info.tmp, Node: linux-installation-docker, Next: linux-installation-native, Prev: linux-installation-debian, Up: linux-installation

2.5.7 Deploying MySQL on Linux with Docker

The Docker deployment framework supports easy installation and configuration of MySQL Server. This section explains how to use a MySQL Server Docker image.

You need to have Docker installed on your system before you can use a MySQL Server Docker image. See Install Docker (https://docs.docker.com/engine/installation/) for instructions.

Warning:

Beware of the security concerns with running Docker containers. See Docker security (https://docs.docker.com/engine/security/) for details.

The instructions for using the MySQL Docker container are divided into two sections.

 File: manual.info.tmp, Node: docker-mysql-getting-started, Next: docker-mysql-more-topics, Prev: linux-installation-docker, Up: linux-installation-docker

2.5.7.1 Basic Steps for MySQL Server Deployment with Docker ...........................................................

Warning:

The MySQL Docker images maintained by the MySQL team are built specifically for Linux platforms. Other platforms are not supported, and users using these MySQL Docker images on them are doing so at their own risk. See *note the discussion here: deploy-mysql-nonlinux-docker. for some known limitations for running these containers on non-Linux operating systems.

Downloading a MySQL Server Docker Image

Important:

For users of MySQL Enterprise Edition: A subscription is required to use the Docker images for MySQL Enterprise Edition. Subscriptions work by a Bring Your Own License model; see How to Buy MySQL Products and Services (https://www.mysql.com/buy-mysql/) for details.

Downloading the server image in a separate step is not strictly necessary; however, performing this step before you create your Docker container ensures your local image is up to date. To download the MySQL Community Edition image, run this command:

 docker pull mysql/mysql-server:TAG

The TAG is the label for the image version you want to pull (for example, '5.6', '5.7', '8.0', or 'latest'). If :TAG is omitted, the 'latest' label is used, and the image for the latest GA version of MySQL Community Server is downloaded. Refer to the list of tags for available versions on the mysql/mysql-server page in the Docker Hub (https://hub.docker.com/r/mysql/mysql-server/tags/).

To download the MySQL Community Edition image from the Oracle Container Registry (OCR), run this command:

 docker pull container-registry.oracle.com/mysql/mysql-server:TAG

To download the MySQL Enterprise Edition image from the OCR, you need to first accept the license agreement on the OCR and log in to the container repository with your Docker client:

Download the Docker image for MySQL Enterprise Edition from the OCR with this command:

 docker pull  container-registry.oracle.com/mysql/enterprise-server:TAG

There are different choices for TAG, corresponding to different versions of MySQL Docker images provided by the OCR:

To download the MySQL Enterprise Edition image, visit the My Oracle Support (https://support.oracle.com/) website, sign in to your Oracle account, and perform these steps once you are on the landing page:

Unzip the downloaded '.zip' archive to obtain the tarball inside ('mysql-enterprise-server-VERSION.tar'), and then load the image by running this command:

 docker load -i mysql-enterprise-server-VERSION.tar

You can list downloaded Docker images with this command:

 $> docker images
 REPOSITORY           TAG                 IMAGE ID            CREATED             SIZE
 mysql/mysql-server   latest              3157d7f55f8d        4 weeks ago         241MB

Starting a MySQL Server Instance

To start a new Docker container for a MySQL Server, use the following command:

 docker run --name=CONTAINER_NAME -d IMAGE_NAME:TAG

The image name can be obtained using the 'docker images' command, as explained in *note docker-download-image::. The '--name' option, for supplying a custom name for your server container, is optional; if no container name is supplied, a random one is generated.

For example, to start a new Docker container for the MySQL Community Server, use this command:

 docker run --name=mysql1 -d mysql/mysql-server:5.7

To start a new Docker container for the MySQL Enterprise Server with a Docker image downloaded from the OCR, use this command:

 docker run --name=mysql1 -d container-registry.oracle.com/mysql/enterprise-server:5.7

To start a new Docker container for the MySQL Enterprise Server with a Docker image downloaded from My Oracle Support, use this command:

 docker run --name=mysql1 -d mysql/enterprise-server:5.7

If the Docker image of the specified name and tag has not been downloaded by an earlier 'docker pull' or 'docker run' command, the image is now downloaded. Initialization for the container begins, and the container appears in the list of running containers when you run the 'docker ps' command. For example:

 $> docker ps
 CONTAINER ID   IMAGE                COMMAND                  CREATED             STATUS                              PORTS                NAMES
 a24888f0d6f4   mysql/mysql-server   "/entrypoint.sh my..."   14 seconds ago      Up 13 seconds (health: starting)    3306/tcp, 33060/tcp  mysql1

The container initialization might take some time. When the server is ready for use, the 'STATUS' of the container in the output of the 'docker ps' command changes from '(health: starting)' to '(healthy)'.

The '-d' option used in the 'docker run' command above makes the container run in the background. Use this command to monitor the output from the container:

 docker logs mysql1

Once initialization is finished, the command's output is going to contain the random password generated for the root user; check the password with, for example, this command:

 $> docker logs mysql1 2>&1 | grep GENERATED
 GENERATED ROOT PASSWORD: Axegh3kAJyDLaRuBemecis&EShOs

Connecting to MySQL Server from within the Container

Once the server is ready, you can run the note 'mysql': mysql. client within the MySQL Server container you just started, and connect it to the MySQL Server. Use the 'docker exec -it' command to start a note 'mysql': mysql. client inside the Docker container you have started, like the following:

 docker exec -it mysql1 mysql -uroot -p

When asked, enter the generated root password (see the last step in note docker-starting-mysql-server:: above on how to find the password). Because the 'MYSQL_ONETIME_PASSWORD' option is true by default, after you have connected a note 'mysql': mysql. client to the server, you must reset the server root password by issuing this statement:

 mysql> ALTER USER 'root'@'localhost' IDENTIFIED BY 'PASSWORD';

Substitute PASSWORD with the password of your choice. Once the password is reset, the server is ready for use.

Container Shell Access

To have shell access to your MySQL Server container, use the 'docker exec -it' command to start a bash shell inside the container:

 $> docker exec -it mysql1 bash
 bash-4.2#

You can then run Linux commands inside the container. For example, to view contents in the server's data directory inside the container, use this command:

 bash-4.2# ls /var/lib/mysql
 auto.cnf    ca.pem      client-key.pem  ib_logfile0  ibdata1  mysql       mysql.sock.lock     private_key.pem  server-cert.pem  sys
 ca-key.pem  client-cert.pem  ib_buffer_pool  ib_logfile1  ibtmp1   mysql.sock  performance_schema  public_key.pem   server-key.pem

Stopping and Deleting a MySQL Container

To stop the MySQL Server container we have created, use this command:

 docker stop mysql1

'docker stop' sends a SIGTERM signal to the *note 'mysqld': mysqld. process, so that the server is shut down gracefully.

Also notice that when the main process of a container (*note 'mysqld': mysqld. in the case of a MySQL Server container) is stopped, the Docker container stops automatically.

To start the MySQL Server container again:

 docker start mysql1

To stop and start again the MySQL Server container with a single command:

 docker restart mysql1

To delete the MySQL container, stop it first, and then use the 'docker rm' command:

 docker stop mysql1

 docker rm mysql1

If you want the Docker volume for the server's data directory to be deleted at the same time, add the '-v' option to the 'docker rm' command.

Upgrading a MySQL Server Container

Important:

Follow these steps to upgrade a Docker installation of MySQL 5.6 to 5.7:

More Topics on Deploying MySQL Server with Docker

For more topics on deploying MySQL Server with Docker like server configuration, persisting data and configuration, server error log, and container environment variables, see *note docker-mysql-more-topics::.

 File: manual.info.tmp, Node: docker-mysql-more-topics, Next: deploy-mysql-nonlinux-docker, Prev: docker-mysql-getting-started, Up: linux-installation-docker

2.5.7.2 More Topics on Deploying MySQL Server with Docker .........................................................

Note:

Most of the sample commands below have 'mysql/mysql-server' as the Docker image repository when that has to be specified (like with the 'docker pull' and 'docker run' commands); change that if your image is from another repository--for example, replace it with 'container-registry.oracle.com/mysql/enterprise-server' for MySQL Enterprise Edition images downloaded from the Oracle Container Registry (OCR), or 'mysql/enterprise-server' for MySQL Enterprise Edition images downloaded from My Oracle Support (https://support.oracle.com/).

The Optimized MySQL Installation for Docker

Docker images for MySQL are optimized for code size, which means they only include crucial components that are expected to be relevant for the majority of users who run MySQL instances in Docker containers. A MySQL Docker installation is different from a common, non-Docker installation in the following aspects:

Configuring the MySQL Server

When you start the MySQL Docker container, you can pass configuration options to the server through the 'docker run' command. For example:

 docker run --name mysql1 -d mysql/mysql-server:TAG --character-set-server=utf8mb4 --collation-server=utf8mb4_col

The command starts your MySQL Server with 'utf8mb4' as the default character set and 'utf8mb4_col' as the default collation for your databases.

Another way to configure the MySQL Server is to prepare a configuration file and mount it at the location of the server configuration file inside the container. See *note docker-persisting-data-configuration:: for details.

Persisting Data and Configuration Changes

Docker containers are in principle ephemeral, and any data or configuration are expected to be lost if the container is deleted or corrupted (see discussions here (https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/)). Docker volumes (https://docs.docker.com/engine/admin/volumes/volumes/), however, provides a mechanism to persist data created inside a Docker container. At its initialization, the MySQL Server container creates a Docker volume for the server data directory. The JSON output for running the 'docker inspect' command on the container has a 'Mount' key, whose value provides information on the data directory volume:

 $> docker inspect mysql1
 ...
  "Mounts": [
             {
                 "Type": "volume",
                 "Name": "4f2d463cfc4bdd4baebcb098c97d7da3337195ed2c6572bc0b89f7e845d27652",
                 "Source": "/var/lib/docker/volumes/4f2d463cfc4bdd4baebcb098c97d7da3337195ed2c6572bc0b89f7e845d27652/_data",
                 "Destination": "/var/lib/mysql",
                 "Driver": "local",
                 "Mode": "",
                 "RW": true,
                 "Propagation": ""
             }
         ],
 ...

The output shows that the source folder' /var/lib/docker/volumes/4f2d463cfc4bdd4baebcb098c97d7da3337195ed2c6572bc0b89f7e845d27652/_data', in which data is persisted on the host, has been mounted at '/var/lib/mysql', the server data directory inside the container.

Another way to preserve data is to bind-mount (https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-or-volumes) a host directory using the '--mount' option when creating the container. The same technique can be used to persist the configuration of the server. The following command creates a MySQL Server container and bind-mounts both the data directory and the server configuration file:

 docker run --name=mysql1 \
 --mount type=bind,src=/PATH-ON-HOST-MACHINE/MY.CNF,dst=/etc/my.cnf \
 --mount type=bind,src=/PATH-ON-HOST-MACHINE/DATADIR,dst=/var/lib/mysql \
 -d mysql/mysql-server:TAG

The command mounts 'PATH-ON-HOST-MACHINE/MY.CNF' at '/etc/my.cnf' (the server configuration file inside the container), and 'PATH-ON-HOST-MACHINE/DATADIR' at '/var/lib/mysql' (the data directory inside the container). The following conditions must be met for the bind-mounting to work:

Running Additional Initialization Scripts

If there are any '.sh' or '.sql' scripts you want to run on the database immediately after it has been created, you can put them into a host directory and then mount the directory at '/docker-entrypoint-initdb.d/' inside the container. For example:

 docker run --name=mysql1 \
 --mount type=bind,src=/PATH-ON-HOST-MACHINE/SCRIPTS/,dst=/docker-entrypoint-initdb.d/ \
 -d mysql/mysql-server:TAG

Connect to MySQL from an Application in Another Docker Container

By setting up a Docker network, you can allow multiple Docker containers to communicate with each other, so that a client application in another Docker container can access the MySQL Server in the server container. First, create a Docker network:

 docker network create MY-CUSTOM-NET

Then, when you are creating and starting the server and the client containers, use the '--network' option to put them on network you created. For example:

 docker run --name=mysql1 --network=MY-CUSTOM-NET -d mysql/mysql-server

 docker run --name=myapp1 --network=MY-CUSTOM-NET -d myapp

The 'myapp1' container can then connect to the 'mysql1' container with the 'mysql1' hostname and vice versa, as Docker automatically sets up a DNS for the given container names. In the following example, we run the *note 'mysql': mysql. client from inside the 'myapp1' container to connect to host 'mysql1' in its own container:

 docker exec -it myapp1 mysql --host=mysql1 --user=myuser --password

For other networking techniques for containers, see the Docker container networking (https://docs.docker.com/engine/userguide/networking/) section in the Docker Documentation.

Server Error Log

When the MySQL Server is first started with your server container, a *note server error log: error-log. is NOT generated if either of the following conditions is true:

To make MySQL Server generate an error log when either of the two conditions is true, use the '--log-error' option to configure the server to generate the error log at a specific location inside the container. To persist the error log, mount a host file at the location of the error log inside the container as explained in *note docker-persisting-data-configuration::. However, you must make sure your MySQL Server inside its container has write access to the mounted host file.

Known Issues

Docker Environment Variables

When you create a MySQL Server container, you can configure the MySQL instance by using the '--env' option ('-e' in short) and specifying one or more of the following environment variables.

Notes:

 File: manual.info.tmp, Node: deploy-mysql-nonlinux-docker, Prev: docker-mysql-more-topics, Up: linux-installation-docker

2.5.7.3 Deploying MySQL on Windows and Other Non-Linux Platforms with Docker ............................................................................

Warning:

The MySQL Docker images provided by Oracle are built specifically for Linux platforms. Other platforms are not supported, and users running the MySQL Docker images from Oracle on them are doing so at their own risk. This section discusses some known issues for the images when used on non-Linux platforms.

Known Issues for using the MySQL Server Docker images from Oracle on Windows include:

 File: manual.info.tmp, Node: linux-installation-native, Next: linux-installation-juju, Prev: linux-installation-docker, Up: linux-installation

2.5.8 Installing MySQL on Linux from the Native Software Repositories

Many Linux distributions include a version of the MySQL server, client tools, and development components in their native software repositories and can be installed with the platforms' standard package management systems. This section provides basic instructions for installing MySQL using those package management systems.

Important:

Native packages are often several versions behind the currently available release. You also normally cannot install development milestone releases (DMRs), as these are not usually made available in the native repositories. Before proceeding, we recommend that you check out the other installation options described in *note linux-installation::.

Distribution specific instructions are shown below:

 File: manual.info.tmp, Node: linux-installation-juju, Next: using-systemd, Prev: linux-installation-native, Up: linux-installation

2.5.9 Installing MySQL on Linux with Juju

The Juju deployment framework supports easy installation and configuration of MySQL servers. For instructions, see https://jujucharms.com/mysql/.

 File: manual.info.tmp, Node: using-systemd, Prev: linux-installation-juju, Up: linux-installation

2.5.10 Managing MySQL Server with systemd

If you install MySQL using an RPM or Debian package on the following Linux platforms, server startup and shutdown is managed by systemd:

If you install MySQL from a generic binary distribution on a platform that uses systemd, you can manually configure systemd support for MySQL following the instructions provided in the post-installation setup section of the MySQL 5.7 Secure Deployment Guide (https://dev.mysql.com/doc/mysql-secure-deployment-guide/en/).

If you install MySQL from a source distribution on a platform that uses systemd, obtain systemd support for MySQL by configuring the distribution using the '-DWITH_SYSTEMD=1' 'CMake' option. See *note source-configuration-options::.

The following discussion covers these topics:

Note:

On platforms for which systemd support for MySQL is installed, scripts such as note 'mysqld_safe': mysqld-safe. and the System V initialization script are unnecessary and are not installed. For example, note 'mysqld_safe': mysqld-safe. can handle server restarts, but systemd provides the same capability, and does so in a manner consistent with management of other services rather than by using an application-specific program.

One implication of the non-use of *note 'mysqld_safe': mysqld-safe. on platforms that use systemd for server management is that use of '[mysqld_safe]' or '[safe_mysqld]' sections in option files is not supported and might lead to unexpected behavior.

Because systemd has the capability of managing multiple MySQL instances on platforms for which systemd support for MySQL is installed, *note 'mysqld_multi': mysqld-multi. and 'mysqld_multi.server' are unnecessary and are not installed.

Overview of systemd

systemd provides automatic MySQL server startup and shutdown. It also enables manual server management using the 'systemctl' command. For example:

 systemctl {start|stop|restart|status} mysqld

Alternatively, use the 'service' command (with the arguments reversed), which is compatible with System V systems:

 service mysqld {start|stop|restart|status}

Note:

For the 'systemctl' or 'service' commands, if the MySQL service name is not 'mysqld', use the appropriate name. For example, use 'mysql' rather than 'mysqld' on Debian-based and SLES systems.

Support for systemd includes these files:

Configuring systemd for MySQL

To add or change systemd options for MySQL, these methods are available:

To use a localized systemd configuration file, create the '/etc/systemd/system/mysqld.service.d' directory if it does not exist. In that directory, create a file that contains a '[Service]' section listing the desired settings. For example:

 [Service]
 LimitNOFILE=MAX_OPEN_FILES
 PIDFile=/PATH/TO/PID/FILE
 Nice=NICE_LEVEL
 LimitCore=CORE_FILE_LIMIT
 Environment="LD_PRELOAD=/PATH/TO/MALLOC/LIBRARY"
 Environment="TZ=TIME_ZONE_SETTING"

The discussion here uses 'override.conf' as the name of this file. Newer versions of systemd support the following command, which opens an editor and permits you to edit the file:

 systemctl edit mysqld  # RPM platforms
 systemctl edit mysql   # Debian platforms

Whenever you create or change 'override.conf', reload the systemd configuration, then tell systemd to restart the MySQL service:

 systemctl daemon-reload
 systemctl restart mysqld  # RPM platforms
 systemctl restart mysql   # Debian platforms

With systemd, the 'override.conf' configuration method must be used for certain parameters, rather than settings in a '[mysqld]', '[mysqld_safe]', or '[safe_mysqld]' group in a MySQL option file:

For additional information about using systemd rather than note 'mysqld_safe': mysqld-safe, see note mysqld-safe-to-systemd-migration::.

You can set the following parameters in 'override.conf':

Some MySQL parameters are configured using environment variables:

There are multiple ways to specify environment variable values for use by the MySQL server process managed by systemd:

To specify options for *note 'mysqld': mysqld. without modifying systemd configuration files directly, set or unset the 'MYSQLD_OPTS' systemd variable. For example:

 systemctl set-environment MYSQLD_OPTS="--general_log=1"
 systemctl unset-environment MYSQLD_OPTS

'MYSQLD_OPTS' can also be set in the '/etc/sysconfig/mysql' file.

After modifying the systemd environment, restart the server to make the changes effective:

 systemctl restart mysqld  # RPM platforms
 systemctl restart mysql   # Debian platforms

For platforms that use systemd, the data directory is initialized if empty at server startup. This might be a problem if the data directory is a remote mount that has temporarily disappeared: The mount point would appear to be an empty data directory, which then would be initialized as a new data directory. As of MySQL 5.7.20, to suppress this automatic initialization behavior, specify the following line in the '/etc/sysconfig/mysql' file (create the file if it does not exist):

 NO_INIT=true

Configuring Multiple MySQL Instances Using systemd

This section describes how to configure systemd for multiple instances of MySQL.

Note:

Because systemd has the capability of managing multiple MySQL instances on platforms for which systemd support is installed, *note 'mysqld_multi': mysqld-multi. and 'mysqld_multi.server' are unnecessary and are not installed. This is true as of MySQL 5.7.13 for RPM platforms, 5.7.19 for Debian platforms.

To use multiple-instance capability, modify the 'my.cnf' option file to include configuration of key options for each instance. These file locations are typical:

For example, to manage two instances named 'replica01' and 'replica02', add something like this to the option file:

RPM platforms:

 [mysqld@replica01]
 datadir=/var/lib/mysql-replica01
 socket=/var/lib/mysql-replica01/mysql.sock
 port=3307
 log-error=/var/log/mysqld-replica01.log

 [mysqld@replica02]
 datadir=/var/lib/mysql-replica02
 socket=/var/lib/mysql-replica02/mysql.sock
 port=3308
 log-error=/var/log/mysqld-replica02.log

Debian platforms:

 [mysqld@replica01]
 datadir=/var/lib/mysql-replica01
 socket=/var/lib/mysql-replica01/mysql.sock
 port=3307
 log-error=/var/log/mysql/replica01.log

 [mysqld@replica02]
 datadir=/var/lib/mysql-replica02
 socket=/var/lib/mysql-replica02/mysql.sock
 port=3308
 log-error=/var/log/mysql/replica02.log

The replica names shown here use '@' as the delimiter because that is the only delimiter supported by systemd.

Instances then are managed by normal systemd commands, such as:

 systemctl start mysqld@replica01
 systemctl start mysqld@replica02

To enable instances to run at boot time, do this:

 systemctl enable mysqld@replica01
 systemctl enable mysqld@replica02

Use of wildcards is also supported. For example, this command displays the status of all replica instances:

 systemctl status 'mysqld@replica*'

For management of multiple MySQL instances on the same machine, systemd automatically uses a different unit file:

In the unit file, '%I' and '%i' reference the parameter passed in after the '@' marker and are used to manage the specific instance. For a command such as this:

 systemctl start mysqld@replica01

systemd starts the server using a command such as this:

 mysqld --defaults-group-suffix=@%I ...

The result is that the '[server]', '[mysqld]', and '[mysqld@replica01]' option groups are read and used for that instance of the service.

Note:

On Debian platforms, AppArmor prevents the server from reading or writing '/var/lib/mysql-replica*', or anything other than the default locations. To address this, you must customize or disable the profile in '/etc/apparmor.d/usr.sbin.mysqld'.

Note:

On Debian platforms, the packaging scripts for MySQL uninstallation cannot currently handle 'mysqld@' instances. Before removing or upgrading the package, you must stop any extra instances manually first.

Migrating from mysqld_safe to systemd

Because *note 'mysqld_safe': mysqld-safe. is not installed on platforms that use systemd to manage MySQL, options previously specified for that program (for example, in an '[mysqld_safe]' or '[safe_mysqld]' option group) must be specified another way:

 File: manual.info.tmp, Node: uln-installation, Next: solaris-installation, Prev: linux-installation, Up: installing