From 2a8297bee5417a76fbe87dd0361dbfecdeb76022 Mon Sep 17 00:00:00 2001 From: Joe Brockmeier Date: Sun, 23 Jun 2013 14:05:19 -0500 Subject: [PATCH] Adding instructions for restarting MySQL on Debian/Ubuntu systems, since the name of the service differs. Found during Hack Day. --- docs/en-US/database-replication.xml | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/docs/en-US/database-replication.xml b/docs/en-US/database-replication.xml index bb144579ddf..8ca80713732 100644 --- a/docs/en-US/database-replication.xml +++ b/docs/en-US/database-replication.xml @@ -37,10 +37,14 @@ server_id=1 The server_id must be unique with respect to other servers. The recommended way to achieve this is to give the master an ID of 1 and each slave a sequential number greater than 1, so that the servers are numbered 1, 2, 3, etc. - Restart the MySQL service: + Restart the MySQL service. On RHEL/CentOS systems, use: # service mysqld restart + On Debian/Ubuntu systems, use: + +# service mysql restart + Create a replication account on the master and give it privileges. We will use the "cloud-repl" user with the password "password". This assumes that master and slave run on the 172.16.1.0/24 network. @@ -90,10 +94,14 @@ innodb_lock_wait_timeout=600 - Restart MySQL. + Restart MySQL. Use "mysqld" on RHEL/CentOS systems: # service mysqld restart + On Ubuntu/Debian systems use "mysql." + +# service mysql restart + Instruct the slave to connect to and replicate from the master. Replace the IP address, password, log file, and position with the values you have used in the previous steps.