Installing MariaDB with yum

You are viewing an old version of this article. View the current version here.

For CentOS, RedHat, and Fedora, it is highly recommended to install from a repository using yum. This page walks you through the simple steps.

Adding the MariaDB YUM Repository

We have YUM repositories for several YUM-based Linux distributions. To easily generate the appropriate MariaDB.repo entry for your distribution, use our online repository generator.

We currently have YUM repositories for CentOS 5, CentOS 6, CentOS 7, RHEL 5, RHEL 6, RHEL 7, and Fedora 21.

Once you have your MariaDB.repo entry, add it to a file under /etc/yum.repos.d/. (We suggest something like /etc/yum.repos.d/MariaDB.repo.)

An example MariaDB.repo file for CentOS 7 is:

[mariadb]
name = MariaDB
baseurl = http://yum.mariadb.org/10.0/centos7-amd64
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1

The example file above includes a gpgkey line to automatically fetch the GPG key we use to sign the repositories. This key enables yum and rpm to verify the integrity of the packages it downloads.

The id of our signing key is 0xcbcb082a1bb943db. The short form of the id is 0x1BB943DB and the full key fingerprint is:

1993 69E5 404B D5FC 7D2F E43B CBCB 082A 1BB9 43DB

If you wish to fix the version to an older version, or do a yum downgrade, you can create a yum repo definition with a baseurl set to a specific version. yum clean metadata is needed if you change an existing repo definition:

[mariadb]
name = MariaDB-5.5.39
baseurl=https://downloads.mariadb.com/files/MariaDB/mariadb-5.5.39/yum/rhel6-amd64/
# alternative: baseurl=http://archive.mariadb.org/mariadb-5.5.39/yum/rhel6-amd64/
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1

Installing MariaDB with YUM

With the repo file in place you can now install MariaDB like so:

sudo yum install MariaDB-server MariaDB-client

If you don't have the MariaDB GPG Signing key installed, YUM will prompt you to install it after downloading the packages (but before installing them).

If the server already has the MariaDB-Galera-server package installed, you might need to remove it prior to installing MariaDB-server (with 'sudo yum remove MariaDB-Galera-server'). No databases are removed when the MariaDB-Galera-server rpm package is removed, but as with any upgrade, it is best to have backups.

Installing TokuDB with YUM

Instructions for installing TokuDB are on the How to Enable TokuDB in MariaDB page.

Installing MariaDB Galera Cluster with YUM

MariaDB until 10.0

Galera Cluster is included in the default MariaDB from 10.1, so the instructions in this section are only required for MariaDB 10.0 and MariaDB 5.5.

The instructions for installing MariaDB Galera Cluster are virtually the same as for installing MariaDB. The setup of the repo file is the same. The only difference is in the install step. Instead of installing the MariaDB-server package, you install the MariaDB-Galera-server and galera packages, like so:

sudo yum install MariaDB-Galera-server MariaDB-client galera

As with MariaDB-server, if you don't have the MariaDB GPG Signing key installed, YUM will prompt you to install it after downloading the packages (but before installing them).

If the server already has the MariaDB-server package installed, you might need to remove it prior to installing MariaDB-Galera-server (with 'sudo yum remove MariaDB-server'). No databases are removed when the MariaDB-server rpm package is removed, but as with any upgrade, it is best to have backups.

See the Galera section of the Knowledgebase for more information on MariaDB Galera Cluster. <</product>>

After Installation

After the installation completes, start MariaDB with:

sudo /etc/init.d/mysql start

Manually Importing the MariaDB Signing Key

If you like, you can manually install the GPG key using the rpm application like so:

sudo rpm --import https://yum.mariadb.org/RPM-GPG-KEY-MariaDB

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.