MariaDB source RPMs (SRPMs) are not packaged on all platforms for which MariaDB RPMs are packaged.

The reason is that MariaDB's build process relies heavily on for a lot of things. In this specific case, MariaDB's build process relies on to build RPMs. The specific package generator that it uses to build RPMs is called .

Support for source RPMs in became usable with MariaDB's build system starting from around . This means that we do not produce source RPMs on platforms where the installed version is older than that.

See also .

_{This page is licensed: CC BY-SA / Gnu FDL}

If you are using DirectAdmin and you encounter any issues with Installing MariaDB with YUM, then the directions below may help. The process is very straightforward.

Or:

Starting httpd:
  httpd:
    Syntax error on line 18 of /etc/httpd/conf/httpd.conf:
    Syntax error on line 1 of /etc/httpd/conf/extra/httpd-phpmodules.conf:
      Cannot load /usr/lib/apache/libphp5.so into server:
        /usr/lib/apache/libphp5.so: undefined symbol: client_errors

RPM Installation

To install the RPMs, there is a quick and easy guide to Installing MariaDB with the RPM Tool. Follow the instructions there.

Necessary Edits

We do not want DirectAdmin's custombuild to remove/overwrite our MariaDB installation whenever an update is performed. To rectify this, disable automatic MySQL installation.

Edit /usr/local/directadmin/custombuild/options.conf and replace mysql_inst=yes with mysql_inst=no

_{This page is licensed: CC BY-SA / Gnu FDL}

This article describes how to download the RPM files and install them using therpm command.

It is highly recommended to Install MariaDB with yum where possible.

Navigate toand choose the desired database version and then select the RPMs that match your Linux distribution and architecture.

Clicking those links takes you to a local mirror. Choose the rpms link and download the desired packages. The packages will be similar to the following:

MariaDB-client-5.2.5-99.el5.x86_64.rpm
MariaDB-debuginfo-5.2.5-99.el5.x86_64.rpm
MariaDB-devel-5.2.5-99.el5.x86_64.rpm
MariaDB-server-5.2.5-99.el5.x86_64.rpm
MariaDB-shared-5.2.5-99.el5.x86_64.rpm
MariaDB-test-5.2.5-99.el5.x86_64.rpm

For a standard server installation you will need to download at least the client, shared, and server RPM files. See About the MariaDB RPM Files for more information about what is included in each RPM package.

After downloading the MariaDB RPM files, you might want to check their signatures. See for more information about checking signatures.

Prior to installing MariaDB, be aware that it will conflict with an existing installation of MySQL. To check whether MySQL is already installed, issue the command:

If necessary, you can remove found MySQL packages before installing MariaDB.

To install MariaDB, use the command:

You should see output such as the following:

Be sure to follow the instructions given in the preceding output and create a password for the root user either by using or by running the /usr/bin/mysql_secure_installation script.

Installing the MariaDB RPM files installs the MySQL tools in the /usr/bin directory. You can confirm that MariaDB has been installed by using the client program. Issuing the command mariadb should give you the MariaDB cursor.

See Also

_{This page is licensed: CC BY-SA / Gnu FDL}

MariaDB RPM packages since are signed.

For MariaDB Community Server, see the MariaDB Community Server RPM / Source Keys section of the GPG page for details on how to import the key used by those repositories.

For MariaDB Enterprise Server, see the MariaDB Enterprise GPG Keys section of the GPG page for details on how to import the key used by those repositories.

To check the signature you first need to import the public part of the key like so:

gpg --keyserver hkp://pgp.mit.edu --recv-keys 1BB943DB

Next you need to let pgp know about the key like so:

gpg --export --armour 1BB943DB > mariadb-signing-key.asc
sudo rpm --import mariadb-signing-key.asc

You can check to see if the key was imported with:

rpm -qa gpg-pubkey*

Once the key is imported, you can check the signature of the MariaDB RPM files by running the something like the following in your download directory:

The output of the above will look something like this (make sure gpg shows up on each OK line):

See Also

_{This page is licensed: CC BY-SA / Gnu FDL}

The following article is about different issues people have encountered when installing MariaDB on RHEL / CentOS.

It is highly recommended to install with yum where possible.

In RHEL/ CentOS it is also possible to install a RPM or a tar ball. The RPM is the preferred version, except if you want to install many versions of MariaDB or install MariaDB in a non standard location.

Replacing MySQL

If you removed an MySQL RPM to install MariaDB, note that the MySQL RPM on uninstall renames /etc/my.cnf to /etc/my.cnf.rpmsave.

After installing MariaDB you should do the following to restore your configuration options:

Unsupported configuration options

If you are using any of the following options in your /etc/my.cnf or other my.cnf file you should remove them. This is also true for MySQL 5.1 or newer:

See also

_{This page is licensed: CC BY-SA / Gnu FDL}

On RHEL, CentOS, Fedora, and other similar Linux RPM based distributions, these provide MariaDB packages. These are supported by those distributions. If you have a particular need for a later version than what is in the distribution, then MariaDB provides repositories for them.

Using repositories rather than installing RPM allows for an ease of update when a new release is made. It is highly recommended to install the relevant RPM packages from MariaDB's repository using yum or dnf. Centos 7 still uses yum, most others use dnf, and SUSE/openSUSE use zypper.

This page walks you through the simple installation steps using dnf and yum.

Adding the MariaDB YUM repository

We currently have YUM/DNF repositories for the following Linux distributions, and for the versions that are in standard (not extended) support:

• Red Hat Enterprise Linux (RHEL)

• CentOS

• Fedora

• openSUSE

Using the MariaDB Package Repository Setup Script

MariaDB provides two helpful scripts for setting up repositories, one for MariaDB Community Server named mariadb_repo_setup, and one for MariaDB Enterprise Server named mariadb_es_repo_setup.

See the section on the page for information on using these scripts.

Using the MariaDB Foundation Repository Configuration Tool

Visit and follow the instructions from there. It will ask for your Linux distribution, desired MariaDB version, and the mirror to use, and will show what files to edit and what commands to run to configure a repository.

Pinning the MariaDB Repository to a Specific Minor Release

If you wish to pin your yum or dnf repository to a specific minor release, or if you would like to downgrade to a specific minor release, then you can configure a repository with the URL hard-coded to that specific minor release.

Updating the MariaDB YUM repository to a New Major Release

MariaDB's yum repository can be updated to a new major release. How this is done depends on how you originally configured the repository.

Updating the Major Release with the MariaDB Package Repository Setup Script

If you configured yum to install from MariaDB Corporation's MariaDB Package Repository by using the , then you can update the major release that the repository uses by running the script again.

Updating the Major Release with the MariaDB Repository Configuration Tool

If you configured yum to install from MariaDB Foundation's MariaDB Repository by using the , then you can update the major release that the repository uses by updating the yum repository configuration file in-place. For example, if you wanted to change the repository from to , and if the repository configuration file was at /etc/yum.repos.d/MariaDB.repo, then you could execute the following:

After that, the repository should refer to .

If the yum repository is pinned to a specific minor release, then the above sed command can result in an invalid repository configuration. In that case, the recommended options are:

• Edit the MariaDB.repo repository file manually.

• Or delete the MariaDB.repo repository file, and then install the repository of the new version with the more robust .

The MariaDB GPG Key

See the page for information on the various keys used by MariaDB.

Installing MariaDB Packages with YUM/DNF

After the dnf/yum repository is configured, you can install MariaDB by executing the or command. The specific command that you would use would depend on which specific packages that you want to install.

Installing the Most Common Packages

To Install the most common packages, execute the following command:

Installing MariaDB Server

To Install MariaDB Server, execute the following command:

Installing MariaDB Galera Cluster with YUM

You need to install the galera-4 package to obtain the 4 wsrep provider library.

To install MariaDB Galera Cluster, you could execute the following command:

If you haven't yet imported the MariaDB GPG public key, then yum will prompt you to import it after it downloads the packages, but before it prompts you to install them.

See for more information on MariaDB Galera Cluster.

Installing MariaDB Clients and Client Libraries with YUM

has been included as the client library (staticly linked). However, the package name for the client library has not been changed.

To Install the clients and client libraries, execute the following command:

If you want compile your own programs against MariaDB Connector/C, execute the following command:

Installing mariadb-backup with YUM

To install , execute the following command:

Installing Plugins with YUM

Some may also need to be installed.

For example, to install the password validation plugin, execute the following command:

Installing Debug Info Packages with YUM

The MariaDB yum repository also contains packages. These package may be needed when .

Installing Debug Info for the Most Common Packages with YUM

To install for the most common packages, execute the following command:

All packages have their debuginfo by appending -debuginfo to the package name.

Installing Debug Info for MariaDB Server with YUM

To install for MariaDB Server, execute the following command:

Installing Older Versions from the Repository

The MariaDB yum repository contains the last few versions of MariaDB. To show what versions are available, use the following command:

The output shows the available versions. For example:

The MariaDB repository in this example contains MariaDB 12.1.2, 12.0.2, and 11.8.2; and the appstream repository contains MariaDB 10.3.39.

To install an older version of a package instead of the latest version we just need to specify the package name, a dash, and then the version number. And we only need to specify enough of the version number for it to be unique from the other available versions.

However, when installing an older version of a package, if dependencies need to be installed, then it will automatically choose to install the latest versions of those packages, which can sometimes break those dependencies. To ensure that all MariaDB packages are on the same version in this scenario, it is necessary to specify them all.

The MariaDB packages that the MariaDB-server package depend on are: MariaDB-client, MariaDB-shared, and MariaDB-common. Therefore, to install MariaDB 12.0.2 from this yum repository, we could do the following (putting the version in a variable and each package on its own line so things are cleaner):

For MariaDB Enterprise it is necessary to specify the release part of the version number as well, but with an underscore (_) instead of a dash (-), as that is how dnf/yum see the version number. For example, for MariaDB Enterprise Server 11.8.5-2 you would specify the version as 11.8.5_2. For example:

The rest of the install and setup process is as normal.

After Installation

After the installation is complete, you can with:

If you are using , then keep in mind that the first node will have to be .

_{This page is licensed: CC BY-SA / Gnu FDL}

On SLES, OpenSUSE, and other similar Linux distributions, it is highly recommended to install the relevant RPM packages from MariaDB's repository using zypper.

This page walks you through the simple installation steps using zypper.

Adding the MariaDB ZYpp repository

We currently have ZYpp repositories for the following Linux distributions:

• SUSE Linux Enterprise Server (SLES) 12

• SUSE Linux Enterprise Server (SLES) 15

• OpenSUSE 15

• OpenSUSE 42

Using the MariaDB Package Repository Setup Script

If you want to install MariaDB with zypper, then you can configure zypper to install from MariaDB Corporation's MariaDB Package Repository by using the .

MariaDB Corporation provides a MariaDB Package Repository for several Linux distributions that use zypper to manage packages. This repository contains software packages related to MariaDB Server, including the server itself, , , , and . The MariaDB Package Repository setup script automatically configures your system to install packages from the MariaDB Package Repository.

To use the script, execute the following command:

Note that this script also configures a repository for and a repository for MariaDB Tools, which currently only contains and its dependencies.

See for more information.

Using the MariaDB Repository Configuration Tool

If you want to install MariaDB with zypper, then you can configure zypper to install from MariaDB Foundation's MariaDB Repository by using the .

The MariaDB Foundation provides a MariaDB repository for several Linux distributions that use zypper to manage packages. This repository contains software packages related to MariaDB Server, including the server itself, , , , and . The MariaDB Repository Configuration Tool can easily generate the appropriate commands to add the repository for your distribution.

For example, if you wanted to use the repository to install on SLES 15, then you could use the following commands to add the MariaDB zypper repository:

Pinning the MariaDB Repository to a Specific Minor Release

If you wish to pin the zypper repository to a specific minor release, or if you would like to downgrade to a specific minor release, then you can create a zypper repository with the URL hard-coded to that specific minor release.

Updating the MariaDB ZYpp repository to a New Major Release

MariaDB's zypper repository can be updated to a new major release. How this is done depends on how you originally configured the repository.

Updating the Major Release with the MariaDB Package Repository Setup Script

If you configured zypper to install from MariaDB Corporation's MariaDB Package Repository by using the , then you can update the major release that the repository uses by running the script again.

Updating the Major Release with the MariaDB Repository Configuration Tool

If you configured zypper to install from MariaDB Foundation's MariaDB Repository by using the , then you can update the major release that the repository uses by removing the repository for the old version and adding the repository for the new version.

First, you can remove the repository for the old version by executing the following command:

After that, you can add the repository for the new version. For example, if you wanted to use the repository to install on SLES 15, then you could use the following commands to add the MariaDB zypper repository:

After that, the repository should refer to .

Importing the MariaDB GPG Public Key

Before MariaDB can be installed, you also have to import the GPG public key that is used to verify the digital signatures of the packages in our repositories. This allows the zypper and rpm utilities to verify the integrity of the packages that they install.

See the page for information on the various keys used by MariaDB.

The utility can be used to import this key. For example:

Once the GPG public key is imported, you are ready to install packages from the repository.

Installing MariaDB Packages with ZYpp

After the zypper repository is configured, you can install MariaDB by executing the command. The specific command that you would use would depend on which specific packages that you want to install.

Installing the Most Common Packages with ZYpp

To Install the most common packages, execute the following command:

Installing MariaDB Server with ZYpp

To Install MariaDB Server, execute the following command:

Installing MariaDB Galera Cluster with ZYpp

You also need to install the galera-4 package to obtain the 4 wsrep provider library.

To install MariaDB Galera Cluster, you could execute the following command:

If you haven't yet imported the MariaDB GPG public key, then zypper will prompt you to import it after it downloads the packages, but before it prompts you to install them.

See for more information on MariaDB Galera Cluster.

Installing MariaDB Clients and Client Libraries with ZYpp

has been included as the client library. However, the package name for the client library has not been changed.

To Install the clients and client libraries, execute the following command:

Installing mariadb-backup with ZYpp

To install , execute the following command:

Installing Plugins with ZYpp

Some may also need to be installed.

For example, to install the password validation plugin, execute the following command:

Installing Debug Info Packages with ZYpp

The MariaDB zypper repository also contains packages. These package may be needed when .

Installing Debug Info for the Most Common Packages with ZYpp

To install for the most common packages, execute the following command:

Installing Debug Info for MariaDB Server with ZYpp

To install for MariaDB Server, execute the following command:

Installing Debug Info for MariaDB Clients and Client Libraries with ZYpp

has been included as the client library. However, the package name for the client library has not been changed.

To install for the clients and client libraries, execute the following command:

Installing Debug Info for mariadb-backup with ZYpp

To install for , execute the following command:

Installing Debug Info for Plugins with ZYpp

For some , may also need to be installed.

For example, to install for the password validation plugin, execute the following command:

Installing Older Versions from the Repository

The MariaDB zypper repository contains the last few versions of MariaDB. To show what versions are available, use the following command:

In the output you will see the available versions.

To install an older version of a package instead of the latest version we just need to specify the package name, a dash, and then the version number. And we only need to specify enough of the version number for it to be unique from the other available versions.

However, when installing an older version of a package, if zypper has to install dependencies, then it will automatically choose to install the latest versions of those packages. To ensure that all MariaDB packages are on the same version in this scenario, it is necessary to specify them all.

The core packages required for a server installation include MariaDB-server, MariaDB-client, MariaDB-shared, MariaDB-backup, and MariaDB-common. For MariaDB 12.3 and later, you must also explicitly include the MariaDB-server-galera package if cluster functionality is required.

Therefore, to install from this zypper repository, we would do the following:

To install (including Galera support):"

The rest of the install and setup process is as normal.

After Installation

After the installation is complete, you can .

If you are using , then keep in mind that the first node will have to be .

_{This page is licensed: CC BY-SA / Gnu FDL}

This guide provides the detailed steps for installing MariaDB 10.1.21 via individual RPM packages on CentOS 7. The process involves installing dependencies, then the main packages, and resolving potential conflicts as they appear.

The RPMs needed for the installation are available from the MariaDB website. The required packages for this guide are:

Step-by-Step Installation

1. Install Basic Dependencies

Available RPM Packages

The available RPM packages depend on the specific MariaDB release series.

List of RPM Packages in MariaDB

Removed RPM Packages

Occasionally, RPM packages are removed from MariaDB. This could be because they are no longer needed, or because they were for features or storage engines that have been removed from MariaDB.

Some examples of removed RPMs are:

Installing RPM Packages

Preferably, you should install MariaDB RPM packages using the package manager of your Linux distribution, for example yum orzypper. But you can also use the lower-level rpm tool.

Actions Performed by RPM Packages

Users and Groups Created

When the aria-server RPM package is installed, it will create a user and group named mysql, if it does not already exist.

See Also