MySQL master-slave configuration problem collation

The database needs to be built in the previous time line. Because you do not want to back up the database, you intend to clone the database virtual machine directly to a new one, and then configure Master-slave synchronization. I have not done so before, so I have not encountered any problems, today to put together a bit of the problems encountered.

192.168.3.1 database (Master)---Cloning---> 192.168.3.2 database (slave)

1. After cloning, turn on Master's Binlog log and authorize.

2.slave configuration, point to Master, synchronize data.

Mysql>Change MASTER to     -Master_host='192.168.3.1',     -Master_user='Slaveuser',     -Master_password='Password',     -Master_port=3306,     -Master_log_file='mysql-bin.000001',     -Master_log_pos= -; Query OK,0Rows affected,2Warnings (0.02Sec

3. The following problems have been encountered:

Question one:

1872 (HY000): Slave failed to initialize relay log info structure from the

Workaround:

Stop Slave;reset Slave;start slave;

Question two:

Last_io_error:fatal error:the slave I/O thread stops because master and slave have equal MySQL server UUIDs; These uuids must is different for replication to work.

Workaround:

Modify the auto.conf file, change the UUID different from the main library, and restart MySQL.

MySQL master-slave configuration problem collation