MySQL Forums
Forum List  »  Replication

Re: Mysql 5.7.10 Master-Master replication stops with 1032 error
Posted by: Abdulla Saiyed
Date: September 05, 2016 10:33PM

Hi Rick,

Below is the logs from the slave when the replication failed.
Can you please suggest the suitable solution to resolve this issue and implement master master replication without any failure :


2016-06-01T10:20:38.297290Z 69222 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000001' position 3820018
2016-06-01T10:21:25.692905Z 69221 [ERROR] Error reading packet from server for channel '': Lost connection to MySQL server during query (server_errno=2013)
2016-06-01T10:21:25.692955Z 69221 [Note] Slave I/O thread killed while reading event for channel ''
2016-06-01T10:21:25.692967Z 69221 [Note] Slave I/O thread exiting for channel '', read up to log 'mysql-bin.000001', position 4011942
2016-06-01T10:21:40.921580Z 69220 [Note] 'CHANGE MASTER TO FOR CHANNEL '' executed'. Previous state master_host='10.100.201.19', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='10.100.201.19', master_port= 3306, master_log_file='mysql-bin.000001', master_log_pos= 24505, master_bind=''.
2016-06-01T10:21:56.717079Z 69223 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2016-06-01T10:21:56.717865Z 69224 [Note] Slave SQL thread for channel '' initialized, starting replication in log 'mysql-bin.000001' at position 24505, relay log '/u01/mysql_data/data/log_bin/mysql-relay-bin.000001' position: 4
2016-06-01T10:21:56.717998Z 69223 [Note] Slave I/O thread for channel '': connected to master 'replication@10.100.201.19:3306',replication started in log 'mysql-bin.000001' at position 24505
2016-06-01T10:21:56.774081Z 69224 [ERROR] Slave SQL for channel '': Could not execute Update_rows event on table crestel_whitespace.crm_crmentity_seq; Can't find record in 'crm_crmentity_seq', Error_code: 1032; handler error HA_ERR_END_OF_FILE; the event's master log mysql-bin.000001, end_log_pos 24990, Error_code: 1032
2016-06-01T10:21:56.774103Z 69224 [Warning] Slave: Can't find record in 'crm_crmentity_seq' Error_code: 1032
2016-06-01T10:21:56.774108Z 69224 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000001' position 24714
2016-06-01T10:24:01.980954Z 69223 [ERROR] Error reading packet from server for channel '': Lost connection to MySQL server during query (server_errno=2013)
2016-06-01T10:24:01.980997Z 69223 [Note] Slave I/O thread killed while reading event for channel ''
2016-06-01T10:24:01.981007Z 69223 [Note] Slave I/O thread exiting for channel '', read up to log 'mysql-bin.000001', position 248882
2016-06-01T10:24:27.313993Z 69220 [Note] 'CHANGE MASTER TO FOR CHANNEL '' executed'. Previous state master_host='10.100.201.19', master_port= 3306, master_log_file='mysql-bin.000001', master_log_pos= 248882, master_bind=''. New state master_host='10.100.201.19', master_port= 3306, master_log_file='mysql-bin.000001', master_log_pos= 5133, master_bind=''.
2016-06-01T10:24:32.095106Z 69225 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2016-06-01T10:24:32.096031Z 69225 [Note] Slave I/O thread for channel '': connected to master 'replication@10.100.201.19:3306',replication started in log 'mysql-bin.000001' at position 5133
2016-06-01T10:24:32.103004Z 69226 [Note] Slave SQL thread for channel '' initialized, starting replication in log 'mysql-bin.000001' at position 5133, relay log '/u01/mysql_data/data/log_bin/mysql-relay-bin.000001' position: 4
2016-06-01T10:24:32.146356Z 69226 [ERROR] Slave SQL for channel '': Could not execute Update_rows event on table crestel_data_cdma.crm_crmentity_seq; Can't find record in 'crm_crmentity_seq', Error_code: 1032; handler error HA_ERR_END_OF_FILE; the event's master log mysql-bin.000001, end_log_pos 5407, Error_code: 1032
2016-06-01T10:24:32.146392Z 69226 [Warning] Slave: Can't find record in 'crm_crmentity_seq' Error_code: 1032
2016-06-01T10:24:32.146403Z 69226 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000001' position 5133
2016-06-01T10:38:18.959182Z 69227 [Note] Aborted connection 69227 to db: 'unconnected' user: 'root' host: 'localhost' (Got timeout reading communication packets)
2016-06-01T11:13:14.744301Z 69225 [ERROR] Error reading packet from server for channel '': Lost connection to MySQL server during query (server_errno=2013)
2016-06-01T11:13:14.744453Z 69225 [Note] Slave I/O thread killed while reading event for channel ''
2016-06-01T11:13:14.744472Z 69225 [Note] Slave I/O thread exiting for channel '', read up to log 'mysql-bin.000001', position 6321805
2016-06-01T11:13:16.688514Z 69229 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2016-06-01T11:13:16.689411Z 69229 [Note] Slave I/O thread for channel '': connected to master 'replication@10.100.201.19:3306',replication started in log 'mysql-bin.000001' at position 6321805




Regards,
J

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Mysql 5.7.10 Master-Master replication stops with 1032 error
4008
September 05, 2016 10:33PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.