Deployment includes installing, configuring, upgrading, downgrading, migration from other DBMSs, and automated deployment options. Here's an overview of what you can find in this section.

Users need to run , without parameters to create a data directory, e.g

Then you can start server like this

If you like to customize the server instance (data directory, install as service etc), please refer to

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

MariaDB Server does not currently provide a .pkg installer for macOS. For information about how to install MariaDB Server on macOS using Homebrew, see .

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

Unsupported Versions of Windows

Recent versions of MariaDB may not install on unsupported Windows versions. See to find the final supported versions.

Available deployment methods are component-specific.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

A MariaDB ID is a free account that provides:

• Customer access to MariaDB database product downloads

Create A MariaDB ID

You can register for a MariaDB ID with a social login or a traditional email/password.

Create a using one of the following Single sign-on methods:

• Sign up using your Google Account

• Sign up using your GitHub Account

• Sign up using your LinkedIn Account

Or use your email address:

• Enter your email address and press next.

• Click the reset button. A password link will appear in your email.

• Once you set a new password, the MariaDB account page will appear.

Obtaining Support

MariaDB Corporation provides commercial support and services for MariaDB database products.

To contact us with questions, or if you need assistance:

• If you are able to login to your MariaDB ID,

• If you do not have a MariaDB ID or are unable to login,

\

MariaDB RPM packages since are signed.

The key we use has an id of 1BB943DB and the key fingerprint is:

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

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:

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

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}

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:

RPM Installation

To install the RPMs, there is a quick and easy guide to . 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}

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}

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 cmake for a lot of things. In this specific case, MariaDB's build process relies on CMake CPack Package Generators to build RPMs. The specific package generator that it uses to build RPMs is called CPackRPM.

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

See also Building MariaDB from a Source RPM.

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

mariadb-install-db initializes the MariaDB data directory and creates the system tables in the mysql database, if they do not exist. MariaDB uses these tables to manage privileges, roles, and plugins. It also uses them to provide the data for the help command in the mariadb client.

mariadb-install-db works by starting MariaDB Server's mysqld process in --bootstrap mode and sending commands to create the system tables and their content.

There is a version specifically for Windows, mysql_install_db.exe.

To invoke mariadb-install-db, use the following syntax:

For the options supported by , see .

For the option groups read by , see .

See for information on the installation process.

See for information on how to troubleshoot the installation process.

See Also

• The Windows version of mariadb-install-db:

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

If you see the error message:

symbol mysql_get_server_name, version libmysqlclient_16 not defined in file libmysqlclient.so.16 with link time reference

...then you are probably trying to use the mysql command-line client from MariaDB with libmysqlclient.so from MySQL.

The symbol mysql_get_server_name() is something present in the MariaDB source tree and not in the MySQL tree.

If you have both the MariaDB client package and the MySQL client packages installed this error will happen if your system finds the MySQL version oflibmysqlclient.so first.

To figure out which library is being linked in dynamically (for instance, the wrong one) use the 'ldd' tool.

or

For example:

You can then use your package manager's tools to find out which package the library belongs to.

On CentOS the command to find out which package installed a specific file is:

On Debian-based systems, the command is:

Here's an example of locating the library and finding out which package it belongs to on an Ubuntu system:

The above shows that the mysql command-line client is using the library /usr/lib/libmysqlclient.so.16 and that library is part of the libmariadbclient16 Ubuntu package. Unsurprisingly, the mysql command-line client works perfectly on this system.

If the answer that came back had been something other than a MariaDB package, then it is likely there would have been issues with running the MariaDB mysql client application.

If the library that the system tries to use is not from a MariaDB package, the remedy is to remove the offending package (and possibly install or re-install the correct package) so that the correct library can be used.

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

PHP5 may give an error if used with the old connect method:

'mysql_connect(): Headers and client library minor version mismatch. Headers:50156 Library:50206'

This is because the library wrongly checks and expects that the client library must be the exact same version as PHP was compiled with. You would get the same error if you tried to upgrade just the MySQL client library without upgrading PHP at the same time.

Ways to fix this issue:

1. Switch to using the mysqlnd driver in PHP (Recommended solution).

2. Run with a lower :

1. Recompile PHP with the MariaDB client libraries.

2. Use your original MySQL client library with the MariaDB.

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

This article lists some typical errors that may happen when you try to use an incompatible MariaDB binary on a linux system:

The following example errors are from trying to install MariaDB built for SuSE 11.x on a SuSE 9.0 server:

> scripts/mysql_install_db
./bin/my_print_defaults: /lib/i686/libc.so.6: 
  version `GLIBC_2.4' not found (required by ./bin/my_print_defaults)

and

> ./bin/mysqld --skip-grant &
./bin/mysqld: error while loading shared libraries: libwrap.so.0:
cannot open shared object file: No such file or directory

If you see either of the above errors, the binary MariaDB package you installed is not compatible with your system.

The options you have are:

• Find another MariaDB package or tar from the that matches your system.

• Alternatively, and .

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

After running apt-upgrade mariadb, it's possible that apt shows a fail in trying to start the server, but in fact the database is up and running, which then provokes apt to remain in a non finished state.

For example:

# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up mariadb-server-10.1 (10.1.10+maria-1~trusty) ...
 * Stopping MariaDB database server mysqld
   ...done.
 * Starting MariaDB database server mysqld
   ...fail!
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing package mariadb-server-10.1 (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mariadb-server:
 mariadb-server depends on mariadb-server-10.1 (= 10.1.10+maria-1~trusty); however:
  Package mariadb-server-10.1 is not configured yet.
 
dpkg: error processing package mariadb-server (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
 mariadb-server-10.1
 mariadb-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

This situation could occur if the timeout for the init script was too short. For example, see MDEV-9382, a situation where the timeout was 30 seconds, but the server was taking 48 seconds to start.

To overcome this, the timeout needs to be increased. This can be achieved as follows:

• On systems where systemd is not enabled/supported: The timeout can be increased by setting MYSQLD_STARTUP_TIMEOUT either directly in the script or via the command line. The init script also sources /etc/default/mariadb, so it can also be used to set MYSQLD_STARTUP_TIMEOUT to persistently change the startup timeout.

• On systems that support systemd: The startup timeout can be increased by setting option.

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

MariaDB is in Gentoo, so the steps to build it are:

1. Synchronize your tree with\

   Copy

   emerge --sync

2. Build MariaDB using\

   Copy

   emerge mariadb

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

How to create a source tar.gz file.

First Setup your build environment.

Then use automake/configure/make to generate the tar file:

BUILD/autorun.sh
./configure --with-plugin-xtradb
make dist

This creates a source file with a name like mysql-5.3.2-MariaDB-beta.tar.gz

See also the generic build instructions.

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

Buildroot

is a way to cross compile MariaDB and other packages into a root filesystem. In the menuconfig you need to enable "Enable C++ Support" first under "Toolchain". After C++ is enabled MariaDB is an option under "Target Packages" ->"Libraries" -> "Databases" -> "mysql support" -> "mysql variant" -> "mariadb". Also enable the "mariadb server" below the "mysql support" option.

Below are instructions for creating your own Debian repository. The instructions are based on

Using the Debian repository you just created

One needs to add a new file to the /etc/apt/sources.list.d/ directory. For instance a new file called mariadb.list

Instructions on compiling MariaDB on musl-based operating systems (Alpine)

The instructions on this page will help you compile from source. Links to more complete instructions for specific platforms can be found on the page.

The following two articles should help you get your Solaris machine prepared to build MariaDB (just ignore the parts about installing buildbot):

For some distributions you can build MariaDB from a source RPM. (See also Why Source RPMs (SRPMs) Aren't Packaged For Some Platforms).

You can build it as follows:

using dnf

On RHEL8 you might need to start with:

sudo dnf config-manager --set-enabled codeready-builder-beta-for-rhel-8-x86_64-rpms

Then, on all dnf distributions:

using yum

using zypper

Or (to avoid building as root):

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

MariaDB Corporation provides package tarballs for some MariaDB database products.

Package tarballs provide multiple benefits:

• Package tarballs are compressed tar archives that contain software packages.

• Software packages can be installed using the operating system's package manager without relying on a remote repository.

• RPM (.rpm) files are distributed for CentOS, Red Hat Enterprise Linux (RHEL), and SUSE Linux Enterprise Server (SLES).

• DEB (.deb) files are distributed for Debian and Ubuntu.

If you want to deploy MariaDB database products without using a package tarball, are available. Available deployment methods are component-specific.

Use Cases

MariaDB database products can be deployed with package tarballs to support use cases, such as:

• Transfer the package tarball to an air-gapped network for installation without an internet connection

• Install software using a package manager without configuring a package repository

• Automatically install missing dependencies using a package manager

Compatibility

The following MariaDB database products can be deployed using package tarballs:

• MariaDB Community Server 10.5

• MariaDB Community Server 10.6

• MariaDB Enterprise Server 10.5

• MariaDB Enterprise Server 10.6

Download a Package Tarball

MariaDB Corporation provides package tarballs (.debs.tar, .rpms.tar) to support customers who leverage in-house package repositories to distribute software to their servers. Secure any such repository to prevent outside access.

MariaDB Corporation provides multiple interfaces to download package tarballs.

Installation From Package Tarball

Once downloaded and extracted, you can:

• Install .rpm packages (RHEL, CentOS, and SLES): rpm -i

• Install .deb packages (Debian, Ubuntu): dpkg -i

• Install from the simple package repositories included in the tarball. Missing dependencies will be resolved when using the apt

Installation loads software to the system. This software requires configuration before the database server is ready for use.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

By default all plugins are enabled and built as dynamic .so (or .dll) modules. If a plugin does not support dynamic builds, it is not built at all.

Use PLUGIN_xxx cmake variables. They can be set on the command line with -DPLUGIN_xxx=value or in the cmake gui. Supported values are

Note that unlike autotools, cmake tries to configure and build incrementally. You can modify one configuration option and cmake will only rebuild the part of the tree affected by it. For example, when you do cmake -DWITH_EMBEDDED_SERVER=1 in the already-built tree, it will make libmysqld to be built, but no other configuration options will be changed or reset to their default values.

In particular this means that if you have run, for examplecmake -DPLUGIN_OQGRAPH=NO and later you want to restore the default behavior (with OQGraph being built) in the same build tree, you would need to runcmake -DPLUGIN_OQGRAPH=DYNAMIC

Alternatively, you might simply delete the CMakeCache.txt file — this is the file where cmake stores current build configuration — and rebuild everything from scratch.

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

In the event that you are using the Linux-based operating system Ubuntu or any of its derivatives and would like to compile MariaDB from source code, you can do so using the MariaDB source repository for the release that interests you.

Before you begin, install the software-properties-common, devscripts and equivs packages.

Installing Build Dependencies

MariaDB requires a number of packages to compile from source. Fortunately, you can use the MariaDB repositories to retrieve the necessary code for the version you want. Use the tool to determine how to set up the MariaDB repository for your release of Ubuntu, the version of MariaDB that you want to install, and the mirror that you want to use.

First add the authentication key for the repository, then add the repository.

Once the repository is set up, you can use apt-get to retrieve the build dependencies. MariaDB packages supplied by Ubuntu and packages supplied by the MariaDB repository have the same base name of mariadb-server. You need to specify the specific version you want to retrieve.

Building MariaDB

Once you have the base dependencies installed, you can retrieve the source code and start building MariaDB. The source code is available on GitHub. Use the --branch option to specify the particular version of MariaDB you want to build.

The source code includes scripts to install the remaining build dependencies. For Ubuntu, they're located in the debian/ directory. Navigate into the repository and run the autobake-deb.sh script. Then use

Further Dependencies

In the event that there are still build dependencies that are not satisfied, use mk-build-deps to generate a build dependency deb to use in installing the remaining packages.

Then, call the autobake-deb.sh script again to build MariaDB.

After Building

After building the packages, it is a good idea to put them in a repository. See the page for instructions.

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

These best practices warrant consideration, but are not expected to apply to every business or in every situation. Recommendations here are not mandatory.

General Recommendations

We recommend that you:

MariaDB Corporation provides package repositories, including the MariaDB Enterprise Repository and the MariaDB Community Repository, that can be used to install MariaDB products using the operating system's package manager. Local mirrors of the package repositories can be used for local deployments.

Local package repository mirrors provide multiple benefits:

• MariaDB Corporation's official package repositories are the source for the local mirror.

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

It is highly recommended to 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:

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

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

The mariadb-install-db.exe utility is the Windows equivalent of .

Functionality

The functionality of mariadb-install-db.exe is comparable with the shell script mariadb-install-db

In the event that you are using the Linux-based operating system Debian or any of its direct derivatives and would like to compile MariaDB from source code, you can do so using the MariaDB source repository for the release that interests you. For Ubuntu and its derivatives, see .

Before you begin, install the software-properties-common and devscripts packages:

Sometimes, one needs to have MariaDB compiled with Vanilla XtraDB. This page describes the process to do this. The process is rather crude, as my goal was just a once-off compile for testing (that is, not packaging or shipping) purposes.

The process is applicable to and XtraDB from Percona Server 5.1.61.

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

To generate RPM packages from the build, supply the -DRPM=xxx flag to CMake, where the value xxx is the name of the distribution you're building for. For example, centos7 or rocky8 or fedora39 or sles15.

What these do are controlled in the following CMake files:

• cmake/cpack_rpm.cmake

How to generate binary tar.gz files.

• .

• with your preferred options/plugins.

If the binaries are already built, you can generate a binary tarball with

In the event that you are using the Linux-based operating system Fedora or any of its derivatives and would like to compile MariaDB from source code, you can do so using the MariaDB build in the official repositories.

Installing Build Dependencies

MariaDB requires a number of packages to compile from source. Fortunately, you can use the package in the Fedora repository to retrieve most of the relevant build dependencies through DNF.

Running DNF in this way pulls the build dependencies for the release of MariaDB compiled by your version of Fedora. These may not be all the dependencies you need to build the particular version of MariaDB you want to use, but it will retrieve most of them.

MariaDB Corporation customers can use a Customer Download Token to download MariaDB database products using command-line tools or automation. This page provides instructions on how to retrieve and use the Customer Download Token.

Alternatively, customers can download MariaDB database products using a web browser from the MariaDB Enterprise Download page without a Customer Download Token if they are logged in with their MariaDB ID.

Retrieve Customer Download Token

MariaDB Corporation customers can retrieve their Customer Download Token through the MariaDB Customer Portal.

To retrieve the Customer Download Token for your account:

1. Navigate to the .

2. Log in using your .

3. Copy the Customer Download Token.

Use the Customer Download Token

MariaDB Corporation customers can use their Customer Download Token for multiple operations.

Choose the procedure for your desired operation and substitute your Customer Download Token for CUSTOMER_DOWNLOAD_TOKEN:

Configure MariaDB Enterprise Repository

MariaDB Corporation provides the MariaDB Enterprise Repository to install MariaDB database products using package managers on CentOS / RHEL (YUM), Debian / Ubuntu (APT), and SLES (ZYpp).

The MariaDB Enterprise Repository is configured using the mariadb_es_repo_setup script, which requires the Customer Download Token to be provided via the --token option.

For additional information, see "".

Download Binary Files

MariaDB Corporation provides an interface to download binary files using command-line tools or automation.

Binary files can be downloaded using command-line tools or automation from the MariaDB Download interface with the Customer Download Token. The URL is in the following format:

Download a binary file using the following procedure:

1. In your web browser, visit the MariaDB Download interface for the specific MariaDB database product:

   • MariaDB Enterprise Server

   • MariaDB MaxScale

or using curl:

Log in to MariaDB Enterprise Docker Registry

Docker is an open platform for developing, shipping, and running applications that allows you to separate your applications from your infrastructure. MariaDB Corporation provides the .

The MariaDB Enterprise Docker Registry provides Docker images for MariaDB Enterprise Server. The Docker images for MariaDB Enterprise Server are currently beta maturity, so they are not currently recommended for production.

For additional information, see "".

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

Architectural Changes

Binary and Process Renaming

MariaDB Enterprise Server 10.5 completes the transition to MariaDB-prefixed names for all executables.

• Process Identification: While symbolic links (e.g., mysqld) are provided for backward compatibility, the primary server binary is now mariadbd.

• Monitoring Alert: When started via systemd or mariadbd-safe, the process will identify as mariadbd in the system process list.

Security and Privileges

Granularity (The "SUPER" Split)

In 10.5, the SUPER privilege has been deconstructed into several smaller, granular privileges to improve security.

Configuration and Include Paths

Debian and Ubuntu Path Logic

Beginning with 10.5, the configuration loading logic on Debian and Ubuntu has shifted:

• Directory Priority: The directory /etc/mysql/mariadb.conf.d/ now uses numeric prefixes to dictate loading order.

• Enterprise Overrides: The mariadb-enterprise.cnf file is typically loaded last, potentially overriding user-defined settings in 50-server.cnf.

Pre-Upgrade Requirements

Mandatory Clean Shutdown

Upgrading from 10.4 to 10.5 after a crash is not supported if the redo log was created in 10.4.

• Requirement: You must perform a clean shutdown (setting SET GLOBAL innodb_fast_shutdown = 0 is recommended) before initiating the upgrade.

• Redo Log Adjustment: If innodb-log-files-in-group is set to 2, it must be changed to 1 on the 10.4 instance, followed by a restart and a final clean shutdown before moving to 10.5.

Critical Parameter Shifts

The MariaDB project signs their MariaDB packages for Debian, Ubuntu, Fedora, and Red Hat. This page documents information about the keys that we use and have used.

MariaDB Community Server Debian / Ubuntu key

Our MariaDB Community Server repositories for Debian "Sid" and the Ubuntu 16.04 and beyond "Xenial" use the following GPG signing key. As detailed in MDEV-9781, APT 1.2.7 (and later) prefers SHA2 GPG keys and now prints warnings when a repository is signed using a SHA1 key like our previous GPG key. We have created a SHA2 key for use with these.

Information about this key:

• The short Key ID is: 0xC74CD1D8

• The long Key ID is: 0xF1656F24C74CD1D8

• The full fingerprint of the key is: 177F 4010 FE56 CA33 3630 0305 F165 6F24 C74C D1D8

• Usage of the apt-key command is deprecated in the latest versions of Debian and Ubuntu, and the replacement method is to download the keyring file to the /etc/apt/trusted.gpg.d/ directory. This can be done with the following:

MariaDB Community Server RPM / Source Keys

MariaDB Enterprise GPG Keys

MariaDB MaxScale GPG Keys

Configuring Repositories

See the page for details on using the mariadb_repo_setup and mariadb_es_repo_setup scripts to configure repositories that use these keys.

See the on configuring MariaDB Foundation repositories that use these keys.

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

MariaDB was originally designed as a drop-in replacement of MySQL, with more features, new storage engines, fewer bugs, and better performance, but you can also install it alongside MySQL. (This can be useful, for example, if you want to migrate databases/applications one by one.)

Here are the steps to install MariaDB near an existing MySQL installation.

• Download the compiled binary tar.gz file that contains the latest version.

• Extract the files in a directory of your choice. In the following, we assume you chose the /opt directory.

• Create data directory and symlinks as below:

• Create group mariadb and user mariadb and set correct ownerships:

• Create a new my.cnf in /opt/mariadb from support files:

• Edit the file /opt/mariadb-data/my.cnf and add custom paths, socket, port, user and the most important of all: data directory and base directory. Finally the file should have at least the following:

• Copy the init.d script from support files in the right location:

• Edit /etc/init.d/mariadb replacing mysql with mariadb as below:

The trickiest part will be the last changes to this file. You need to tell mariadb to use only one configuration file. In the start section after**$bindir/mysqld_safe** add --defaults-file=/opt/mariadb-data/my.cnf. Finally the lines should look like:

The same change needs to be made to the command below in the wait_for_ready() function so that the mariadb start command can properly listen for the server start. In the wait_for_ready() function, after $bindir/mariadb-admin add --defaults-file=/opt/mariadb-data/my.cnf. The lines should look like:

• Run by explicitly giving it the my.cnf file as argument:

• Now you can start MariaDB by

• Make MariaDB start at system start:

• Finally test that you have both instances running:

What about MariaDB Upgrades ?

By having the mariadb.socket, my.cnf file and databases in /opt/mariadb-data means that if you want to upgrade the MariaDB version you will only need to:

• Extract the new version from the archive in /opt near the current version,

• Stop MariaDB.

• Change the symlink mariadb to point to the new directory.

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

Binary tarballs (bintars) are compressed tar archives that contain pre-compiled executables, libraries, and other deployment dependencies. They can usually be installed on any modern Linux distribution.

MariaDB Binary tarballs are named following the pattern: mariadb-VERSION-OS.tar.gz. Be sure to download the correct version for your machine.

Benefits of Binary Tarballs

Binary tarballs provide multiple benefits:

• They are highly OS independent. As long as you get the bintar for the architecture, GLIBC version, and if you are using systemd or not, the bintar should work almost anywhere.

• You do not need to be root to use them.

Installing binary tarballs

To install the , unpack the distribution into the directory of your choice and run the script.

In the example below, we install MariaDB in the /usr/local/mysql directory (this is the default location for MariaDB for many platforms). However, any other directory should work too.

We install the binary with a symlink to the original name. This is done so that you can easily change MariaDB versions just by moving the symlink to point to another directory.

Ensure You Use the Correct my.cnf Files

MariaDB searches for the configuration files '/etc/my.cnf' (on some systems '/etc/mysql/my.cnf') and '~/.my.cnf'. If you have an old my.cnf file (maybe from a system installation of MariaDB or MySQL), you need to take care that you don't accidentally use the old one with your new binary .tar installation.

The normal solution for this is to ignore the my.cnf file in /etc when you use the programs in the tar file.

This is done by in your home directory and telling ,, and possibly to only use this one with the option '--defaults-file=~/.my.cnf'. Note that this has to be the first option for the above commands!

Installing MariaDB as root in /usr/local/mysql

If you have root access to the system, you probably want to install MariaDB under the user and group 'mysql' (to keep compatibility with MySQL installations):

The symlinking with ln -s is recommended as it makes it easy to install many MariaDB versions at the same time (for easy testing, upgrading, downgrading, etc).

If you are installing MariaDB to replace MySQL, then you can leave out the call to mariadb-install-db. Instead, shut down MySQL. MariaDB should find the path to the data directory from your old /etc/my.cnf file (path may vary depending on your system).

To start mariadbd, you should now do:

To test the connection, modify your $PATH so you can invoke clients such as , , etc.

You may want to modify your .bashrc or .bash_profile to make it permanent.

Installing MariaDB as Not root in Any Directory

Below, change /usr/local to the directory of your choice.

If you have problems with the above gunzip command line, you can instead, if you have gnu tar, do:

To start mariadbd, you should now do:

Auto Start of mariadbd

You can get mariadbd (the MariaDB server) to autostart by copying the file mysql.server file to the right place.

The exact place depends on your system. The mysql.server file contains instructions on how to use and fine tune it.

For systemd installation, the mariadb.service file will need to be copied from the support-files/systemd folder to the /usr/lib/systemd/system/ folder.

Note that, by default, the /usr/ directory is write protected by systemd, though, so when having the data directory in /usr/local/mysql/data as per the instructions above, you also need to make that directory writable. You can do so by adding an extra service include file:

After this, you can start the service using this command:

Stop the service with this command:

Please refer to the page for further information.

Post Installation

After this, remember to set proper passwords for all accounts accessible from untrusted sources, to avoid exposing the host to security risks!

Also consider using the to when your system boots.

On systems using systemd, instead, enable automatic startup during system boot with this command:

For details on the exact steps used to build the binaries, see the .

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

Shortly after the release we became aware of some installation issues with the Debian and Ubuntu repositories. These issues were fixed in , but due to how apt works, steps need to be taken to solve the broken dependencies before upgrading.

We know of three scenarios when dependencies were broken. The steps to fix each of them are pretty much the same, only the list of broken dependencies and hence the list of packages to take care of them differs. The basic idea is to downgrade those certain packages to 5.5.32 temporarily before upgrading them to 5.5.33a.

If you ran into issues when moving from to , look through each of the three scenarios to see which one applies to you and then follow the steps to apply that fix.

Applying the fix

To get your system ready to apply the fix, do the following:

• Comment out the standard repo in the /etc/apt/sources.list or /etc/apt/sources.list.d/mariadb.repo file (or wherever you have the repositories configured).

• Add a repository to the sources.list. The easiest way is to add the following. Just replace '{os}' and '{dist}' with the appropriate values.

For example, on Debian Wheezy the line would be:

And on Ubuntu Raring the line would be:

• Then run 'sudo apt-get update'

• Then 'sudo apt-get install' the list of packages to downgrade as given in the applicable section below.

• Next, modify our sources.list to remove the 5.5.32 repo and switch back to the normal 5.5 repo

5.5.32 server + 5.5.32 client upgraded to the initial (17 Sep 2013) release of 5.5.33

In this first scenario, both client and server were partially upgraded to 5.5.33 before the process aborted. The problem looks like this:

To fix it, the following server and client packages need to be temporarily downgraded to 5.5.32 (replace 'wheezy' with the name of whatever distribution you are using):

5.5.32 Galera server and 5.5.32 MariaDB client upgraded to 5.5.33

In this scenario, the client upgraded, but Galera-server did not. The problem looks like this:

To fix it, only the client packages need to be temporarily downgraded to 5.5.32 (replace wheezy with whatever your distribution is):

5.3.12 server + 5.3.12 client + 5.5.32 libmariadbclient18 upgraded to 5.5.33

In this scenario, only the library upgraded. The problem looks like this:

To fix it, the library needs to be downgraded to 5.5.32 (replace wheezy with your distribution):

After switching back to the 5.5 repo, the libraries won't get upgraded, they will stay 5.5.32 until you upgrade the server to 5.5.33a.

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

A member of the MariaDB community, Mark <ms (at) it-infrastrukturen (dot) org>, has created some Debian "squeeze" 6.0.4 based, live iso images with or 5.3 pre-installed on them and some Debian "squeeze" 6.0.5 based, live iso images with pre-installed on them.

These live and install images can be used to quickly run a MariaDB server in live mode for learning or testing purposes, or to simplify and speed up off-line installations of Debian-based MariaDB servers onto harddisk.

In the event that you are using the Linux-based operating system CentOS or any of its derivatives, you can optionally compile MariaDB from source code. This is useful in cases where you want use a more advanced release than the one that's available in the official repositories, or when you want to enable certain feature that are not otherwise accessible.

Installing Build Dependencies for

Before you start building MariaDB, you first need to install the build dependencies required to run the compile. CentOS provides a tool for installing build dependencies. The yum-builddep

Prelude

Building MariaDB on macOS relies on the Apple-provided toolchain and Homebrew for dependencies.

You can install the toolchain without XCode (suggested, unless you have XCode installed already) with:

Homebrew is a package manager for macOS which you can install from

The .deb packages provided by MariaDB Foundation's and MariaDB Corporation's repositories are not identical to the official .deb packages provided by Debian's and Ubuntu's default repositories.

The packages provided by MariaDB Foundation's and MariaDB Corporation's repositories are generated using the Debian packaging in MariaDB's official source code. The Debian packaging scripts are specifically in the debian/ directory.

The packages provided by Debian's and Ubuntu's default repositories are generated using the Debian packaging in Debian's mirror of MariaDB's source code, which contains some custom changes. The source tree can be found here:

As a consequence, MariaDB behaves a bit differently if it is installed from Debian's and Ubuntu's default repositories.

Option File Locations

• The located at /etc/mysql/my.cnf is handled by the mechanism when the mysql-common package is installed. It is a symbolic link that references either mysql.cnf or mariadb.cnf depending on whether MySQL or MariaDB is installed. Most of the MariaDB are therefore actually located in /etc/mysql/mariadb.d/.

System Variables

Since there is no system variable difference from the Standard MariaDB.

Options

TLS

• MariaDB binaries from packages provided by Debian's and Ubuntu's default repositories are linked with a different TLS library than MariaDB binaries from packages provided by MariaDB Foundation's and MariaDB Corporation's repositories.

• MariaDB Server binaries:

  • MariaDB Server is statically linked with the bundled libraries in packages provided by Debian's and Ubuntu's default repositories.

Authentication

• The authentication plugin is installed by default in new installations that use the packages provided by Debian's default repositories in Debian 9 and later and Ubuntu's default repositories in Ubuntu 15.10 and later.

• The root@localhost created by will also be created to authenticate via the authentication plugin in these builds.

See Also

More Information

For details, check out the Debian and Ubuntu official repositories:

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

It is relatively straightforward to build MariaDB from source on FreeBSD. When working with an individual host, you can use Ports to compile particular or multiple versions of MariaDB. When working with multiple hosts, you can use Poudriere to build MariaDB once, then serve it as a package to multiple FreeBSD hosts.

Using Ports

The FreeBSD Ports Collection provides a series of Makefiles that you can use to retrieve source code, configure builds, install dependencies and compile software. This allows you to use more advanced releases than what is normally available through the package managers as well as enable any additional features that interest you.

In the event that you have not used Ports before on your system, you need to first fetch and extract the Ports tree. This downloads the Ports tree from FreeBSD and extracts it onto your system, placing the various Makefiles, patches and so on in the /usr/ports/ directory.

In the event that you have used Ports before on this system, run Portsnap again to download and install any updates to the Ports tree.

This ensures that you are using the most up to date release of the Ports tree that is available on your system.

Building MariaDB from Ports

Once Portsnap has installed or updated your Ports tree, you can change into the relevant directory and install MariaDB. Ports for MariaDB are located in the /usr/ports/databases/ directory.

Note that FreeBSD treats the Server and Client as separate packages. The Client is a dependency of the Server, so you only need to build the Server to get both. It also provides a number of different versions. You can search the available ports from . Decide what version of MariaDB you want to install, the change into the relevant directory. Once in the directory, run Make to build MariaDB.

In addition to downloading and building MariaDB, Ports also downloads and build any libraries on which MariaDB depends. Each port it builds will take you to a GUI window where you can select various build options. In the case of MariaDB, this includes various storage engines and specific features you need in your build.

Once you finish building the ports, install MariaDB on your system and clean the directory to free up disk space.

This installs FreeBSD on your server. You can now enable, configure and start the service as you normally would after installing MariaDB from a package.

Using Poudriere

Poudriere is a utility for building FreeBSD packages. It allows you to build MariaDB from a FreeBSD Jail, then serve it as a binary package to other FreeBSD hosts. You may find this is particularly useful when building to deploy multiple MariaDB servers on FreeBSD, such as with Galera Cluster or similar deployments.

Building MariaDB

Once you've configured your host to use Jails and Poudriere, initialize a jail to use in building packages and a jail for managing ports.

This creates two jails, package-builder and local-ports, which you can then use to build MariaDB. Create a text file to define the packages you want to build. Poudriere will build these packages as well as their dependencies. MariaDB is located at databases/mariadb103-server. Adjust the path to match the version you want to install.

Use the options command to initialize the build options for the packages you want Poudriere to compile.

Lastly, use the bulk command to compile the packages.

Using Poudriere Repositories

In order to use Poudriere, you need to set up and configure a web server, such as Nginx or Apache to serve the directory that Poudriere built. For instance, in the case of the above example, you would map to the package-builder jail: /usr/local/poudriere/data/packages/package-builder/.

You may find it useful to map this directory to a sub-domain, for instance httpspkg.example.com or something similar.

Lastly, you need to configure the FreeBSD hosts to use the Poudriere repository you just created. On each host, disable the FreeBSD official repositories and enable your Poudriere repository as an alternative.

Then add the URL for your Poudriere repository to configuration file:

You can then install MariaDB from Poudriere using the package manager.

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

MariaDB uses InnoDB as the default storage engine.

If you want to use Oracle's InnoDB plugin, then you need to compile MariaDB andnot specify --without-plugin-innodb_plugin when configuring. For example, a simple ./configure without any options will do.

When the InnoDB plugin is compiled, the innodb_plugin test suite will test the InnoDB plugin in addition to xtradb:

./mysql-test-run --suite=innodb_plugin

To use the innodb_plugin instead of xtradb you can do (for ):

See Also

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