Latest revision as of 23:18, 21 March 2024

MariaDB is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. It is notable for being led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle.

This is the general documentation for normal and common general usage, for professional usage please use MySQL that is the same as MariaDB but with several modifications focused on production and security!

Installation

The Alpine Linux repositories no longer include the actual MySQL binaries, installing the mysql-* packages will instead install MariaDB.

Installing mariadb will create the user mysql. When the database is initialized, two users will be added to the database: root and mysql. By default these users will only be accessible if you are logged in as the corresponding system user.

apk add mysql mysql-client

Installing the above packages will add the main components of MariaDB to the system: mariadb-cient and mariadb-server. Other available packages are described in the table below, and are listed in order of relevance for a production server.

MySQL name package	Since Alpine:	Brief usage	Related package
mysql	v2	a transitional package that installs mariadb	mariadb
mysql-client	v2	a transitional package that installs the mariadb client tools	mariadb-client
mariadb	v2	server equivalent to mysql-server	mariadb-common
mariadb-client	v2	connection command line and tools	mariadb-common
mariadb-doc	v3.0	manpages for mariadb	man man-pages
mariadb-connector-odbc	edge	coding or making OS level connections, to any DB without libs install	.
mariadb-connector-c	v3.8	coding connection on C sources	mariadb-connector-c-dev
mariadb-backup	v3.8	tool for physical online backups, no longer widely used	.
mariadb-server-utils	v3.8	server commands not widely used, in past was inside MariaDB package	.
mariadb-dev	v3.1	development files for MariaDB	.
mariadb-test	v3.3	testing suite from MariaDB tools	.
mariadb-mytop	v3.9	data performance monitoring	.
mariadb-plugin-rocksdb	v3.9	plain key-value event relational for data	.
mariadb-static	v3.8	static libs for static non depends linking in builds	.
mariadb-embedded	v3.9	the libmysqld identical interface as the C client	mariadb-embedded-dev
mariadb-embedded-dev	v3.9	use the normal mysql.h and link with libmysqld instead of libmysqlclient	mariadb-dev
mariadb-openrc	v3.8	separate scripts, in past was embebed on server package	.

Initialization

The version of MariaDB in the Alpine repositories behave like the MySQL tarball. No graphical tools are included.

The datadir located at /var/lib/mysql must be owned by the mysql user and group. The location of the datadir can be changed by editing the mariadb service file in /etc/init.d. The new location will also need to be set by adding datadir=<YOUR_DATADIR> in the [mysqld] section in a mariadb configuration file.

Normal initialization of mariadb can be done as follows:

Initialize the main mysql database, and the data dir as standardized to /var/lib/mysql by running rc-service mariadb setup
Start the main service. At this point there will be no root password set. rc-service mariadb start
Secure the database by running mysql_secure_installation
Setup permissions for managing others users and databases

Configuration

In order to help with the basic configuration of the database engine, MariaDB provides mysql_secure_installation. This script walks you through the basics of securing the database. The options are explained below.

Enter current password for root (enter for none): If you have previously set up a root password, provide it here and press enter. If not, just press enter.
Switch to unix_socket authentication [Y/n] Setting the root password or using the Unix_socket ensures that only admins can log into engine database. For non-production servers just press "n" to setup a root password, which will give you the response ... skipping.
Change the root password? [Y/n] Here you can change the root password, or set one if needed. Press "Y" and enter the new password.
Remove anonymous users? [Y/n] Remove anonymous users created to log in using socket authentication. Unless you're sure you need this, answer "Y" to remove them.
Disallow root login remotely? [Y/n] Normally, root should only be allowed to connect from 'localhost' in order to protect from password sniffing attempts over the network. Answer "Y".
Remove test database and access to it? [Y/n] By default, MariaDB comes with a database named 'test' that anyone can access. If this is not needed, answer "Y".
Reload privilege tables now? [Y/n] Reloading the privilege tables will ensure that all changes made so far will take effect immediately. Answer "Y".

After the script exits, restart the service with rc-service mariadb restart

To start the database daemon on every boot, run rc-update add mariadb default

Configuration files and customization

Rather than being stored in my.cnf, configuration settings for MariaDB are now organized in separate files. The primary configuration is done by adding files to /etc/my.cnf.d/. User-specific configuration files are stored in ~/.my.cnf. User-specific configuration files are loaded after the system-wide configuration. The locations of the various configuration files are listed below.

Config file	Versions of Alpine	Contents to configure
/etc/mysql/my.cnf	v2 to v3.8	All the directives, global config file
/etc/my.cnf.d/mariadb-server.cnf	since 3.9	First global config file, main directives
$HOME/.my.cnf	all	user name only config directives

As previously mentioned, this page describes basic usage of MariaDB. For professional usage, MySQL should also be referenced.

The following command will configure the server to accept all incoming connections. This should only be done for development, or if the database is not exposed to the Internet or a sensitive network.

For simple installations, disabling hostname search can improve performance, but is only useful for local servers.

Updating or coming from upgrading

When upgrading between Alpine Linux releases, MariaDB may also have a major version change, and the databases should be upgraded to match. The recommended steps in this process are detailed below.

While it may no longer be strictly necessary, it's useful to backup your databases before upgrading the database version.
Update Alpine Linux and the MariaDB/MySQL packages.
Install mariadb-server-utils by running apk add mariadb-server-utils.
Run mysql_upgrade -u root -p script, and provide the password for the root database user.
Restart the service by running rc-service mariadb restart.

If mysql_upgrade fails because MySQL cannot start, try running MySQL in safemode with mysqld_safe --datadir=/var/lib/mysql/, and then run mysql_upgrade -u root -p again.

@@ Line 1: / Line 1: @@
 [https://mariadb.org/ MariaDB] is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. It is notable for being led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle.
-'''This is the general documentation for normal and common general usage, for professional usage please use [[Production DataBases : mysql]] that is the same as MariaDB but with several modifications focused on production and security!'''
+'''This is the general documentation for normal and common general usage, for professional usage please use [[MySQL]] that is the same as MariaDB but with several modifications focused on production and security!'''
 == Installation ==
-Alpine Linux has dummy counterparts packages for those that are not close to that change from ''mysql'' to ''mariadb'' naming packages.
+The Alpine Linux repositories no longer include the actual MySQL binaries, installing the <code>mysql-*</code> packages will instead install MariaDB.
-Take in consideration that the user <code>mysql</code> was created during instalation of packages, in the initialization section two users will be created in database init: <code>root</code> and <code>mysql</code>, and in that point only if are in their respective system accounts, will be able to connect to the database service.
+Installing <code>mariadb</code> will create the user <code>mysql</code>. When the database is initialized, two users will be added to the database: <code>root</code> and <code>mysql</code>. By default these users will only be accessible if you are logged in as the corresponding system user.
-<pre><nowiki>
+{{Cmd|apk add {{pkg|mysql|arch=}} {{pkg|mysql-client|arch=}}}}
-apk add mysql mysql-client
-</nowiki></pre>
-That will install the most used ones.. <code>mariadb-cient</code> and <code>mariadb-server</code>, rest of packages are brief described here for more information, here are listed in orden of relevance for production server
+Installing the above packages will add the main components of MariaDB to the system: <code>mariadb-cient</code> and <code>mariadb-server</code>. Other available packages are described in the table below, and are listed in order of relevance for a production server.
 {| class="wikitable"
@@ Line 19: / Line 17: @@
 ! MySQL name package !! Since Alpine: !! Brief usage !! Related package
 |-
-| mysql || v2 || it's a dummy package to easy install of mariadb || mariadb
+| {{Pkg|mysql}} || v2 || a transitional package that installs mariadb || mariadb
 |-
-| mysql-client || v2 || it's a dummy package to easy install of commands tools || mariadb-client
+| {{Pkg|mysql-client}} || v2 || a transitional package that installs the mariadb client tools || mariadb-client
 |-
-| mariadb || v2 || server equivalent to mysql-server || mariadb-common
+| {{Pkg|mariadb}} || v2 || server equivalent to mysql-server || mariadb-common
 |-
-| mariadb-client || v2 || connection command line and tools || mariadb-common
+| {{Pkg|mariadb-client}} || v2 || connection command line and tools || mariadb-common
 |-
-| mariadb-doc || v3.0 || manpages are there! || man man-pages
+| {{Pkg|mariadb-doc}} || v3.0 || manpages for mariadb || man man-pages
 |-
-| mariadb-connector-odbc || edge || coding or making OS level connections, to any DB without libs install || .
+| {{Pkg|mariadb-connector-odbc}} || edge || coding or making OS level connections, to any DB without libs install || .
 |-
-| mariadb-connector-c || v3.8 || coding connection on C sources || mariadb-connector-c-dev
+| {{Pkg|mariadb-connector-c}} || v3.8 || coding connection on C sources || mariadb-connector-c-dev
 |-
-| mariadb-backup || v3.8 || to external backup devices, not widely used, in past was inside mariadb package || .
+| {{Pkg|mariadb-backup}} || v3.8 || tool for physical online backups, no longer widely used || .
 |-
-| mariadb-server-utils || v3.8 || server commands not widely used, in past was inside mariadb package || .
+| {{Pkg|mariadb-server-utils}} || v3.8 || server commands not widely used, in past was inside MariaDB package || .
 |-
-| mariadb-dev || v3.1 || Need for compilations depends on source code || .
+| {{Pkg|mariadb-dev}} || v3.1 || development files for MariaDB || .
 |-
-| mariadb-test || v3.3 || testing suite from MariaDB tools || .
+| {{Pkg|mariadb-test}} || v3.3 || testing suite from MariaDB tools || .
 |-
-| mariadb-mytop || v3.9 || data performance monitoring || .
+| {{Pkg|mariadb-mytop}} || v3.9 || data performance monitoring || .
 |-
-| mariadb-plugin-rocksdb || v3.9 || plain key-value event relational for data || .
+| {{Pkg|mariadb-plugin-rocksdb}} || v3.9 || plain key-value event relational for data || .
 |-
-| mariadb-static || v3.8 || static libs for static non depends linking in builds || .
+| {{Pkg|mariadb-static}} || v3.8 || static libs for static non depends linking in builds || .
 |-
-| mariadb-embedded || v3.9 || the libmysqld identical interface as the C client || mariadb-embedded-dev
+| {{Pkg|mariadb-embedded}} || v3.9 || the libmysqld identical interface as the C client || mariadb-embedded-dev
 |-
-| mariadb-embedded-dev || v3.9 ||  use the normal mysql.h and link with libmysqld instead of libmysqlclient || mariadb-dev
+| {{Pkg|mariadb-embedded-dev}} || v3.9 ||  use the normal mysql.h and link with libmysqld instead of libmysqlclient || mariadb-dev
 |-
-| mariadb-openrc || v3.8 || separate scripts, in past was embebed on server package || .
+| {{Pkg|mariadb-openrc}} || v3.8 || separate scripts, in past was embebed on server package || .
 |}
 == Initialization ==
-The alpine package of MySQL/MariaDB are like normal tarball of MySQL one, admins must know what they want.. there's no automatic window-like installation here.
+The version of MariaDB in the Alpine repositories behave like the MySQL tarball. No graphical tools are included.
-The ''datadir'' located at <code>/var/lib/mysql</code> must be owned by the mysql user and group. You can modify this behavior but must edit the service file at <code>/etc/init.d</code> directory. Also, you need to set <code><nowiki>datadir=<YOUR_DATADIR></nowiki></code> under section <code>[mysqld]</code> at the config file.
+The ''datadir'' located at {{Path|/var/lib/mysql}} must be owned by the mysql user and group. The location of the ''datadir'' can be changed by editing the <code>mariadb</code> service file in {{Path|/etc/init.d}}. The new location will also need to be set by adding <code><nowiki>datadir=<YOUR_DATADIR></nowiki></code> in the <code>[mysqld]</code> section in a mariadb configuration file.
-# Initialize the main mysql database, and the data dir as standardized to <code>/var/lib/mysql</code> by the rc script.<br>/etc/init.d/mariadb setup
+Normal initialization of mariadb can be done as follows:
-# Then you can start the service but there's no root password set until this point.<br>/etc/init.d/mariadb start
-# Secure the installation by running<code>mysql_secure_installation</code>
+# Initialize the main mysql database, and the data dir as standardized to {{Path|/var/lib/mysql}} by running <code>rc-service mariadb setup</code>
-# Setup permissions for manage others users and databases
+# Start the main service. At this point there will be no root password set. <code>rc-service mariadb start</code>
+# Secure the database by running <code>mysql_secure_installation</code>
+# Setup permissions for managing others users and databases
 == Configuration ==
-In order to finish setup into '''MariaDB''' now provide '''this script called <code>mysql_secure_installation</code> that also are present as <code>mariadb-secure-installation</code>''', too. This script provides minimal and security setup to the database, and here are the questions made explained:
+In order to help with the basic configuration of the database engine, MariaDB provides <code>mysql_secure_installation</code>.
+This script walks you through the basics of securing the database. The options are explained below.
-# '''Enter current password for root (enter for none):''' If you have previously set up a root password, provide it here and press enter, either just push enter. If correctly entered, the response will be <code>OK, successfully used password, moving on...</code>
-#  '''Switch to unix_socket authentication [Y/n]''' Setting the root password or using the Unix_socket ensures that only admins can log into engine database, cos we are not production one just pust "n" to setup a root password, which will give you the response <code>... skipping.</code>
-# '''Change the root password? [Y/n]''' This gives you the opportunity to change the root password to a stronger one if necessary. So enter "Y" and lest type the new password.. be carefully with that can be remembered.
-# '''Remove anonymous users? [Y/n]''' Remove anonymous users created to log in using socket authentication. Answering 'Y', resulting in: <code>... Success!</code>.
-# '''Disallow root login remotely? [Y/n]''' Normally, root should only be allowed to connect from 'localhost' in order to protect from password sniffing attempts over the network. Enter 'Y' to get: <code>... Success!</code>.
-# '''Remove test database and access to it? [Y/n]''' By default, MariaDB comes with a database named 'test' that anyone can access. If this is not needed, 'Y'. The response will be: <code>... Success!</code>.
-# '''Reload privilege tables now? [Y/n]''' Reloading the privilege tables will ensure that all changes made so far will take effect immediately. Answer 'Y' and the response will be: <code>... Success!</code>.
-After responding to each question, restart the service with <code>rc-service mariadb restart</code>
+# '''Enter current password for root (enter for none):''' If you have previously set up a root password, provide it here and press enter. If not, just press enter.
+#  '''Switch to unix_socket authentication [Y/n]''' Setting the root password or using the Unix_socket ensures that only admins can log into engine database. For non-production servers just press "n" to setup a root password, which will give you the response <code>... skipping.</code>
+# '''Change the root password? [Y/n]''' Here you can change the root password, or set one if needed. Press "Y" and enter the new password.
+# '''Remove anonymous users? [Y/n]''' Remove anonymous users created to log in using socket authentication. Unless you're sure you need this, answer "Y" to remove them.
+# '''Disallow root login remotely? [Y/n]''' Normally, root should only be allowed to connect from 'localhost' in order to protect from password sniffing attempts over the network. Answer "Y".
+# '''Remove test database and access to it? [Y/n]''' By default, MariaDB comes with a database named 'test' that anyone can access. If this is not needed, answer "Y".
+# '''Reload privilege tables now? [Y/n]''' Reloading the privilege tables will ensure that all changes made so far will take effect immediately. Answer "Y".
-so to make always work on each restart set to default as <code>rc-update add mariadb default</code>
+After the script exits, restart the service with <code>rc-service mariadb restart</code>
+To start the database daemon on every boot, run <code>rc-update add mariadb default</code>
 === Configuration files and customization ===
-Due today were influenced by systemd standardization, the famous <nowiki>my.cnf</nowiki> are not more the main config file for the server engine. Now only few variables are defined there and all the settings are provided by independent files into the <code>/etc/my.cnf.d/</code> directory, user own config files are under <code>~/.my.cnf</code> config file of each home dir, and are read after global ones; so then we have:
+Rather than being stored in {{Path|my.cnf}}, configuration settings for MariaDB are now organized in separate files. The primary configuration is done by adding files to {{Path|/etc/my.cnf.d/}}. User-specific configuration files are stored in {{Path|~/.my.cnf}}. User-specific configuration files are loaded after the system-wide configuration. The locations of the various configuration files are listed below.
 {| class="wikitable"
 |-
-! Config file !! Path and name !! Versions of Alpine !! Contents to configure
+! Config file !! Versions of Alpine !! Contents to configure
 |-
-| my.cnf || <nowiki>/etc/mysql/my.cnf</nowiki> || v2 to v3.8 || All the directives, Global config file
+| {{Path|/etc/mysql/my.cnf}} || v2 to v3.8 || All the directives, global config file
 |-
-| mariadb-server.cnf || /etc/my.cnf.d/mariadb-server.cnf || since 3.9 || First Global config file, main directives
+| {{Path|/etc/my.cnf.d/mariadb-server.cnf}} || since 3.9 || First global config file, main directives
 |-
-| .my.cnf || <nowiki>$HOME</nowiki> || all || user name only config directives
+| {{path|$HOME/.my.cnf}} || all || user name only config directives
 |}
-As previously pointed here is the general documentation for normal and common general usage, for professional usage please use [[Production DataBases : mysql]] that is the same as MariaDB but with several modifications focused on production and security.
+As previously mentioned, this page describes basic usage of MariaDB. For professional usage, [[MySQL]] should also be referenced.
-Newer system Alpine packages can set in independent files in any case those commands always works and where are not apply just will ignore the output:
-* First lest allowed all incoming connections if we plan to use in our network or remotely, we do not put focus on security cos we must focus on easy usage and/or development:
+* The following command will configure the server to accept all incoming connections. This should only be done for development, or if the database is not exposed to the Internet or a sensitive network.
-<pre>
+{{Cmd|<nowiki>sed -i "s|.*bind-address\s*=.*|bind-address=0.0.0.0|g" /etc/mysql/my.cnf
-<nowiki>
-sed -i "s|.*bind-address\s*=.*|bind-address=0.0.0.0|g" /etc/mysql/my.cnf
 sed -i "s|.*bind-address\s*=.*|bind-address=0.0.0.0|g" /etc/my.cnf.d/mariadb-server.cnf
-</nowiki>
+</nowiki>}}
-</pre>
-* So we are a simple install and not are in domain controller, dont search for hostnames to improve performance responses (ideal for local only servers):
+* For simple installations, disabling hostname search can improve performance, but is only useful for local servers.
-<pre>
+{{Cmd|<nowiki>sed -i "s|.*skip-networking.*|skip-networking|g" /etc/mysql/my.cnf
-<nowiki>
-sed -i "s|.*skip-networking.*|skip-networking|g" /etc/mysql/my.cnf
 sed -i "s|.*skip-networking.*|skip-networking|g" /etc/my.cnf.d/mariadb-server.cnf
-</nowiki>
+</nowiki>}}
-</pre>
 == Updating or coming from upgrading ==
-Major Upgrades between Alpine Linux version are so easy as change the repository version, but the MySQL/MariaDB  engine need some extra steps when this are performed:
+When upgrading between Alpine Linux releases, MariaDB may also have a major version change, and the databases should be upgraded to match. The recommended steps in this process are detailed below.
-Upgrade databases on major releases
-Upon a major version release of mariadb (for example mariadb-10.1.10-1 to mariadb-10.1.18-1), it is wise to upgrade databases:
-# keep the old database (mysql scheme) structure of the engine daemon, currently this are not more the case, today this not make sense anymore
+# While it may no longer be strictly necessary, it's useful to backup your databases before upgrading the database version.
-# upgrade the MariaDB/MySQL packages, of course with must be done if the upgrade process to mayor alpine version does not!
+# Update Alpine Linux and the MariaDB/MySQL packages.
-# run the <code>mysql_upgrade -u root -p</code> script, providing the password or root, (from the new package version) against the old still-running database (mysql scheme). This will produce some error messages; however, the upgrade will succeed.
+# Install mariadb-server-utils by running <code>apk add {{pkg|mariadb-server-utils|arch=}}</code>.
-# Restart the service
+# Run <code>mysql_upgrade -u root -p</code> script, and provide the password for the root database user.
+# Restart the service by running <code>rc-service mariadb restart</code>.
-If are unable to run ''mysql_upgrade'' because MySQL cannot start try run MySQL in safemode with <code>mysqld_safe --datadir=/var/lib/mysql/</code> command and then run the <code>mysql_upgrade -u root -p</code> script.
+If <code>mysql_upgrade</code> fails because MySQL cannot start, try running MySQL in safemode with <code>mysqld_safe --datadir=/var/lib/mysql/</code>, and then run <code>mysql_upgrade -u root -p</code> again.
 = See Also =
-* [[Production DataBases : mysql]]
+* [[MySQL]]
 * [[Production LAMP system: Lighttpd + PHP + MySQL]]
-* [[Alpine newbie developer]]
 [[Category:Newbie]]