Table of Contents [+/-]
After installing MySQL on a Unix-like system, you must initialize the grant tables, start the server, and make sure that the server works satisfactorily. You may also wish to arrange for the server to be started and stopped automatically when your system starts and stops. You should also assign passwords to the accounts in the grant tables.
On a Unix-like system, the grant tables are set up by the mysql_install_db program. For some installation methods, this program is run for you automatically if an existing database cannot be found.
If you install MySQL on Linux using RPM distributions, the server RPM runs mysql_install_db.
Using the native packaging system on many platforms, including Debian Linux, Ubuntu Linux, Gentoo Linux and others, the mysql_install_db command is run for you.
If you install MySQL on Mac OS X using a DMG distribution, the installer runs mysql_install_db.
For other platforms and installation types, including generic binary and source installs, you will need to run mysql_install_db yourself.
The following procedure describes how to initialize the grant tables (if that has not previously been done) and start the server. It also suggests some commands that you can use to test whether the server is accessible and working properly. For information about starting and stopping the server automatically, see Section 5.2, “Starting and Stopping MySQL Automatically”.
After you complete the procedure and have the server running, you should assign passwords to the accounts created by mysql_install_db and perhaps restrict access to test databases. For instructions, see Securing the Initial MySQL Accounts.
In the examples shown here, the server runs under the user ID of
mysql login account. This assumes that such
an account exists. Either create the account if it does not exist,
or substitute the name of a different existing login account that
you plan to use for running the server. For information about
creating the account, see
mysql System User and Group, in
Chapter 1, Installing MySQL on Unix/Linux Using Generic Binaries.
Change location into the top-level directory of your MySQL
installation, represented here by
BASEDIR is the installation
directory for your MySQL instance. It is likely to be
/usr/local. The following steps assume
that you have changed location to this directory.
You will find several files and subdirectories in the
BASEDIR directory. The most
important for installation purposes is the
bin subdirectory, which contains client
programs, the server, and the
directory contains the mysql_install_db
program used to initialize the
database containing the grant tables that store the server
access permissions. You should add the full path name of this
directory to your
PATH environment variable
so that your shell finds the MySQL programs properly. See
If necessary, ensure that the distribution contents are
mysql. If you installed the
mysql, no further action is
required. If you installed the distribution as
root, its contents will be owned by
root. Change its ownership to
mysql by executing the following commands
root in the installation directory. The
first command changes the owner attribute of the files to the
mysql user. The second changes the group
attribute to the
chown -R mysql .shell>
chgrp -R mysql .
If necessary, run the mysql_install_db program to set up the initial MySQL grant tables containing the privileges that determine how users are permitted to connect to the server. You will need to do this if you used a distribution type for which the installation procedure does not run the program for you.
Typically, mysql_install_db needs to be run only the first time you install MySQL, so you can skip this step if you are upgrading an existing installation, However, mysql_install_db does not overwrite any existing privilege tables, so it should be safe to run in any circumstances.
It might be necessary to specify other options such as
mysql_install_db does not identify the
correct locations for the installation directory or data
directory. For example:
bin/mysql_install_db --user=mysql \
The mysql_install_db program creates the
server's data directory with
mysql as the
owner. Under the data directory, it creates directories for
mysql database that holds the grant
tables and the
test database that you can
use to test MySQL. The script also creates privilege table
root and anonymous-user
accounts. The accounts have no passwords initially.
Securing the Initial MySQL Accounts, describes the initial
privileges. Briefly, these privileges permit the MySQL
root user to do anything, and permit
anybody to create or use databases with a name of
test or starting with
The MySQL Access Privilege System, for a complete listing and
description of the grant tables.
For a more secure installation, invoke
mysql_install_db with the
--random-passwords option. This causes it to
assign a random password to the MySQL
accounts, set the “password expired” flag for
those accounts, and remove the anonymous-user MySQL accounts.
For additional details, see
mysql_install_db — Initialize MySQL Data Directory. (Install operations using
RPMs for Unbreakable Linux Network are unaffected because they
do not use mysql_install_db.)
It is important to make sure that the database directories and
files are owned by the
mysql login account
so that the server has read and write access to them when you
run it later. To ensure this if you run
root, include the
--user option as
shown. Otherwise, you should execute the program while logged
mysql, in which case you can omit the
--user option from
If you do not want to have the
database, you can remove it after starting the server, using
the instructions in Securing the Initial MySQL Accounts.
If you have trouble with mysql_install_db at this point, see Section 5.1, “Problems Running mysql_install_db”.
Most of the MySQL installation can be owned by
root if you like. The exception is that the
data directory must be owned by
accomplish this, run the following commands as
root in the installation directory:
chown -R root .shell>
chown -R mysql data
If the plugin directory (the directory named by the
plugin_dir system variable)
is writable by the server, it may be possible for a user to
write executable code to a file in the directory using
SELECT ... INTO
DUMPFILE. This can be prevented by making
plugin_dir read only to the
server or by setting
--secure-file-priv to a
can be made safely.
If you installed MySQL using a source distribution, you may
want to optionally copy one of the provided configuration
files from the
/etc directory. There are
different sample configuration files for different use cases,
server types, and CPU and RAM configurations. If you want to
use one of these standard files, you should copy it to
/etc/mysql/my.cnf and edit and check the
configuration before starting your MySQL server for the first
If you do not copy one of the standard configuration files, the MySQL server will be started with the default settings.
If you want MySQL to start automatically when you boot your
machine, you can copy
support-files/mysql.server to the
location where your system has its startup files. More
information can be found in the
mysql.server script itself, and in
Section 5.2, “Starting and Stopping MySQL Automatically”.
Start the MySQL server:
bin/mysqld_safe --user=mysql &
It is important that the MySQL server be run using an
root) login account. To
ensure this if you run mysqld_safe as
root, include the
--user option as shown.
Otherwise, you should execute the program while logged in as
mysql, in which case you can omit the
--user option from the
For further instructions for running MySQL as an unprivileged user, see How to Run MySQL as a Normal User.
If the command fails immediately and prints
ended, look for information in the error log (which
by default is the
file in the data directory).
If you neglected to create the grant tables by running mysql_install_db before proceeding to this step, the following message appears in the error log file when you start the server:
mysqld: Can't find file: 'host.frm'
If you have other problems starting the server, see Section 5.3, “Starting and Troubleshooting the MySQL Server”. For more information about mysqld_safe, see mysqld_safe — MySQL Server Startup Script.
Use mysqladmin to verify that the server is running. The following commands provide simple tests to check whether the server is up and responding to connections:
The output from mysqladmin version varies slightly depending on your platform and version of MySQL, but should be similar to that shown here:
bin/mysqladmin versionmysqladmin Ver 14.12 Distrib 5.7.6, for pc-linux-gnu on i686 ... Server version 5.7.6 Protocol version 10 Connection Localhost via UNIX socket UNIX socket /var/lib/mysql/mysql.sock Uptime: 14 days 5 hours 5 min 21 sec Threads: 1 Questions: 366 Slow queries: 0 Opens: 0 Flush tables: 1 Open tables: 19 Queries per second avg: 0.000
To see what else you can do with
mysqladmin, invoke it with the
bin/mysqladmin -u root shutdown
Verify that you can start the server again. Do this by using mysqld_safe or by invoking mysqld directly. For example:
bin/mysqld_safe --user=mysql &
If mysqld_safe fails, see Section 5.3, “Starting and Troubleshooting the MySQL Server”.
Run some simple tests to verify that you can retrieve information from the server. The output should be similar to what is shown here:
bin/mysqlshow+--------------------+ | Databases | +--------------------+ | information_schema | | mysql | | test | +--------------------+ shell>
bin/mysqlshow mysqlDatabase: mysql +---------------------------+ | Tables | +---------------------------+ | columns_priv | | db | | event | | func | | help_category | | help_keyword | | help_relation | | help_topic | | host | | plugin | | proc | | procs_priv | | servers | | tables_priv | | time_zone | | time_zone_leap_second | | time_zone_name | | time_zone_transition | | time_zone_transition_type | | user | +---------------------------+ shell>
bin/mysql -e "SELECT Host,Db,User FROM db" mysql+------+--------+------+ | host | db | user | +------+--------+------+ | % | test | | | % | test_% | | +------+--------+------+
There is a benchmark suite in the
sql-bench directory (under the MySQL
installation directory) that you can use to compare how MySQL
performs on different platforms. The benchmark suite is
written in Perl. It requires the Perl DBI module that provides
a database-independent interface to the various databases, and
some other additional Perl modules:
DBI DBD::mysql Data::Dumper Data::ShowTable
sql-bench/Results directory contains
the results from many runs against different databases and
platforms. To run all tests, execute these commands:
If you do not have the
directory, you probably installed MySQL using RPM files other
than the source RPM. (The source RPM includes the
sql-bench benchmark directory.) In this
case, you must first install the benchmark suite before you
can use it. There are separate benchmark RPM files named
that contain benchmark code and data.
If you have a source distribution, there are also tests in its
tests subdirectory that you can run. For
example, to run
execute this command from the top-level directory of your
mysql -vvf test < ./tests/auto_increment.tst
The expected result of the test can be found in the
At this point, you should have the server running. However, none of the initial MySQL accounts have a password, and the server permits permissive access to test databases. To tighten security, follow the instructions in Securing the Initial MySQL Accounts.
The MySQL 5.7 installation procedure creates time
zone tables in the
mysql database but does not
populate them. To do so, use the instructions in
MySQL Server Time Zone Support.
To make it more convenient to invoke programs installed in the
bin directory under the installation
directory, you can add that directory to your
PATH environment variable setting. That enables
you to run a program by typing only its name, not its entire path
name. See Setting Environment Variables.