mariadb-admin

mariadb-admin is an administration program for the mariadbd daemon. It can be used to:

• Monitor what the MariaDB clients are doing (processlist)
• Get usage statistics and variables from the MariaDB server
• Create/drop databases
• Flush (reset) logs, statistics and tables
• Kill running queries.
• Stop the server (shutdown)
• Start/stop replicas
• Check if the server is alive (ping)

Prior to MariaDB 10.5, the client was called mysqladmin. It can still be accessed under this name, via a symlink in Linux, or an alternate binary in Windows.

Using mariadb-admin

The command to use mariadb-admin and the general syntax is:

mariadb-admin [options] command [command-arg] [command [command-arg]] ...

Options

mariadb-admin supports the following options:

Option Files

In addition to reading options from the command-line, mariadb-admin can also read options from option files. If an unknown option is provided to mariadb-admin in an option file, then it is ignored.

The following options relate to how MariaDB command-line tools handles option files. They must be given as the first argument on the command-line:

mariadb-admin is linked with MariaDB Connector/C. However, MariaDB Connector/C does not yet handle the parsing of option files for this client. That is still performed by the server option file parsing code. See MDEV-19035 for more information.

Option Groups

mariadb-admin reads options from the following option groups from option files:

mariadb-admin Variables

Variables can be set with --variable-name=value.

mariadb-admin Commands

mariadb-admin [options] command [command-arg] [command [command-arg]] ...

Command is one or more of the following. Commands may be shortened to a unique prefix.

The shutdown Command and the --wait-for-all-slaves Option

The --wait-for-all-slaves option was first added in MariaDB 10.4.4. When a primary server is shutdown and it goes through the normal shutdown process, the primary kills client threads in random order. By default, the primary also considers its binary log dump threads to be regular client threads. As a consequence, the binary log dump threads can be killed while client threads still exist, and this means that data can be written on the primary during a normal shutdown that won't be replicated. This is true even if semi-synchronous replication is being used.

In MariaDB 10.4 and later, this problem can be solved by shutting down the server with the mariadb-admin utility and by providing the --wait-for-all-slaves option to the utility and by executing the shutdown command with the utility. For example:

mariadb-admin --wait-for-all-slaves shutdown

When the --wait-for-all-slaves option is provided, the server only kills its binary log dump threads after all client threads have been killed, and it only completes the shutdown after the last binary log has been sent to all connected replicas.

See Replication Threads: Binary Log Dump Threads and the Shutdown Process for more information.

Examples

Quick check of what the server is doing:

shell> mariadb-admin status
Uptime: 8023 Threads: 1 Questions: 14 Slow queries: 0 Opens: 15 Flush tables: 1 Open tables: 8 Queries per second avg: 0.1
shell> mariadb-admin processlist
+----+-------+-----------+----+---------+------+-------+------------------+
| Id | User | Host | db | Command | Time | State | Info |
+----+-------+-----------+----+---------+------+-------+------------------+
....
+----+-------+-----------+----+---------+------+-------+------------------+

More extensive information of what is happening 'just now' changing (great for troubleshooting a slow server):

shell> mariadb-admin --relative --sleep=1 extended-status | grep -v " 0 "

Check the variables for a running server:

shell> mariadb-admin variables | grep datadir
| datadir | /my/data/ |

Using a shortened prefix for the version command:

shell> mariadb-admin ver
mariadb-admin from 11.1.0-preview-MariaDB, client 9.1 for linux-systemd (x86_64)
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Server version		11.1.0-preview-MariaDB
Protocol version	10
Connection		localhost via TCP/IP
TCP port		11100
Uptime:			3 min 21 sec

Threads: 1  Questions: 1  Slow queries: 0  Opens: 17  Open tables: 10  Queries per second avg: 0.004

Other Ways To Stop mariadbd (Unix)

If you get the error:

mariadb-admin: shutdown failed; error: 'Access denied; you need (at least one of) the SHUTDOWN privilege(s) for this operation'

It means that you didn't use mariadb-admin with a user that has the SUPER or SHUTDOWN privilege.

If you don't know the user password, you can still take the mariadbd process down with a system kill command:

kill -SIGTERM pid-of-mariadbd-process

The above is identical to mariadb-admin shutdown.

On windows you should use:

NET STOP MySQL

You can use the SHUTDOWN command from any client.

See Also

• SHUTDOWN command
• mytop, a 'top' like program for MariaDB/MySQL that allows you to see what the server is doing. A mytop optimized for MariaDB is included in MariaDB 5.3