If you have followed the instructions but your replication setup is not working, the first thing to do is check the error log for messages. Many users have lost time by not doing this soon enough after encountering problems.
If you cannot tell from the error log what the problem was, try the following techniques:
Verify that the source has binary logging enabled by issuing a
SHOW BINARY LOG STATUSstatement. Binary logging is enabled by default. If binary logging is enabled,
Positionis nonzero. If binary logging is not enabled, verify that you are not running the source with any settings that disable binary logging, such as the
Verify that the
server_idsystem variable was set at startup on both the source and replica and that the ID value is unique on each server.
Verify that the replica is running. Use
SHOW REPLICA STATUSto check whether the
Replica_SQL_Runningvalues are both
Yes. If not, verify the options that were used when starting the replica server. For example,
--skip-replica-startprevents the replication threads from starting until you issue a
If the replica is running, check whether it established a connection to the source. Use
SHOW PROCESSLIST, find the I/O (receiver) and SQL (applier) threads and check their
Statecolumn to see what they display. See Section 19.2.3, “Replication Threads”. If the receiver thread state says
Connecting to master, check the following:
Verify the privileges for the replication user on the source.
Check that the host name of the source is correct and that you are using the correct port to connect to the source. The port used for replication is the same as used for client network communication (the default is
3306). For the host name, ensure that the name resolves to the correct IP address.
Check the configuration file to see whether the
skip_networkingsystem variable has been enabled on the source or replica to disable networking. If so, comment the setting or remove it.
If the source has a firewall or IP filtering configuration, ensure that the network port being used for MySQL is not being filtered.
Check that you can reach the source by using
tracertto reach the host.
If the replica was running previously but has stopped, the reason usually is that some statement that succeeded on the source failed on the replica. This should never happen if you have taken a proper snapshot of the source, and never modified the data on the replica outside of the replication threads. If the replica stops unexpectedly, it is a bug or you have encountered one of the known replication limitations described in Section 19.5.1, “Replication Features and Issues”. If it is a bug, see Section 19.5.5, “How to Report Replication Bugs or Problems”, for instructions on how to report it.
If a statement that succeeded on the source refuses to run on the replica, try the following procedure if it is not feasible to do a full database resynchronization by deleting the replica's databases and copying a new snapshot from the source:
Determine whether the affected table on the replica is different from the source table. Try to understand how this happened. Then make the replica's table identical to the source's and run
If the preceding step does not work or does not apply, try to understand whether it would be safe to make the update manually (if needed) and then ignore the next statement from the source.
If you decide that the replica can skip the next statement from the source, issue the following statements:
mysql> SET GLOBAL sql_replica_skip_counter = N; mysql> START REPLICA;
The value of
Nshould be 1 if the next statement from the source does not use
LAST_INSERT_ID(). Otherwise, the value should be 2. The reason for using a value of 2 for statements that use
LAST_INSERT_ID()is that they take two events in the binary log of the source.
See also SET GLOBAL sql_slave_skip_counter Syntax.
If you are sure that the replica started out perfectly synchronized with the source, and that no one has updated the tables involved outside of the replication threads, then presumably the discrepancy is the result of a bug. If you are running the most recent version of MySQL, please report the problem. If you are running an older version, try upgrading to the latest production release to determine whether the problem persists.