How To Report Replication Bugs Or Problems - Oracle 5.0 Reference Manual

display. See
Connecting to
• Verify the privileges for the user being used for replication on the master.
• Check that the host name of the master is correct and that you are using the correct port to
connect to the master. 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 that networking has not been disabled on the master or slave. Look for the
networking
• If the master 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 master by using
• If the slave was running previously but has stopped, the reason usually is that some statement
that succeeded on the master failed on the slave. This should never happen if you have taken
a proper snapshot of the master, and never modified the data on the slave outside of the slave
thread. If the slave stops unexpectedly, it is a bug or you have encountered one of the known
replication limitations described in
see Section 16.4.5, "How to Report Replication Bugs or
it.
• If a statement that succeeded on the master refuses to run on the slave, try the following procedure
if it is not feasible to do a full database resynchronization by deleting the slave's databases and
copying a new snapshot from the master:
1. Determine whether the affected table on the slave is different from the master table. Try to
understand how this happened. Then make the slave's table identical to the master's and run
START
2. 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 master.
3. If you decide that the slave can skip the next statement from the master, issue the following
statements:
mysql>
mysql>
The value of
or
LAST_INSERT_ID()
2 for statements that use
events in the binary log of the master.
See also
4. If you are sure that the slave started out perfectly synchronized with the master, and that no one
has updated the tables involved outside of the slave thread, 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.

16.4.5. How to Report Replication Bugs or Problems

When you have determined that there is no user error involved, and replication still either does not
work at all or is unstable, it is time to send us a bug report. We need to obtain as much information as
How to Report Replication Bugs or Problems
Section 16.2.1, "Replication Implementation
master, check the following:
[421] option in the configuration file. If present, comment it out or remove it.
SLAVE.
SET GLOBAL sql_slave_skip_counter = N;
START SLAVE;
should be 1 if the next statement from the master does not use
N
[961]. Otherwise, the value should be 2. The reason for using a value of
AUTO_INCREMENT
Section 13.4.2.6, "SET GLOBAL sql_slave_skip_counter
or
ping
Section 16.4.1, "Replication Features and
Problems", for instructions on how to report
or
LAST_INSERT_ID()
1511
Details". If the I/O thread state says
traceroute/tracert
Issues". If it is a bug,
[961] is that they take two
Syntax".
skip-
to reach the host.
AUTO_INCREMENT