# Error on replication, need some help. **URL:** \ **Category:** Other MySQL® Questions\ **Created:** [April 8, 2013, 2:34am UTC](https://forums.percona.com/t/error-on-replication-need-some-help/2033 "2013-04-08T02:34:14Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![warrence](https://avatars.discourse-cdn.com/v4/letter/w/3ab097/32.png) [@warrence](https://forums.percona.com/u/warrence)\ **Post date:** [April 8, 2013, 2:34am UTC](https://forums.percona.com/t/error-on-replication-need-some-help/2033/1 "2013-04-08T02:34:14Z")
Hi, all. I’m new in Percona, i have a master server running Percona xtradb, and a replication slave running in percona too, it replicate just fine. My problem exist on another slave machine which running standard MySQL. Below are the error i get: Last\_Errno: 0 Last\_Error: Could not parse relay log event entry. The possible reasons are: the master’s binary log is corrupted (you can check this by running ‘mysqlbinlog’ on the binary log), the slave’s relay log is corrupted (you can check this by running ‘mysqlbinlog’ on the relay log), a network problem, or a bug in the master’s or slave’s MySQL code. If you want to check the master’s binary log or slave’s relay log, you will be able to know their names by issuing ‘SHOW SLAVE STATUS’ on this slave. Does that mean only Percona Slave can replicate from Percona Master? Or is there setting that i miss out to get Standard MySQL to be able to replicate from Percona Master? Thanks in advance for help. ---
**Author:** ![miguelangelnieto](https://avatars.discourse-cdn.com/v4/letter/m/b9e5f3/32.png) [@miguelangelnieto](https://forums.percona.com/u/miguelangelnieto)\ **Post date:** [April 8, 2013, 5:25am UTC](https://forums.percona.com/t/error-on-replication-need-some-help/2033/2 "2013-04-08T05:25:09Z")
Percona Slave can replicate from a Standard MySQL, there are no incompatibilities at binary log level. That error means that master or slave’s relay log is corrupted and then can’t continue reading it. Can you paste the full SHOW SLAVE STATUS\G and also the version number of master and slaves. ---
**Author:** ![warrence](https://avatars.discourse-cdn.com/v4/letter/w/3ab097/32.png) [@warrence](https://forums.percona.com/u/warrence)\ **Post date:** [April 8, 2013, 12:47pm UTC](https://forums.percona.com/t/error-on-replication-need-some-help/2033/3 "2013-04-08T12:47:59Z")
Master: Server version: 5.5.28-log Percona XtraDB Cluster (GPL), wsrep\_23.7.r3821 Slave: Server version: 5.0.77-log Source distribution Slave\_IO\_State: Waiting for master to send event Master\_Host: \*\*\*\*\*\*.com Master\_User: rep Master\_Port: 3306 Connect\_Retry: 60 Master\_Log\_File: mysql-bin.000070 Read\_Master\_Log\_Pos: 182631007 Relay\_Log\_File: teckkongtbj-relay-bin.2828243 Relay\_Log\_Pos: 534 Relay\_Master\_Log\_File: mysql-bin.000070 Slave\_IO\_Running: Yes Slave\_SQL\_Running: No Replicate\_Do\_DB: csposxe,csposxehq Replicate\_Ignore\_DB: Replicate\_Do\_Table: Replicate\_Ignore\_Table: csposxehq.yiisession,csposxe.reportcontrol,csposxehq.ReportD ata,csposxe.reportdata,csposxe.yiisession Replicate\_Wild\_Do\_Table: Replicate\_Wild\_Ignore\_Table: Last\_Errno: 0 Last\_Error: Could not parse relay log event entry. The possible reasons are: the master’s binary log is corrupted (you can check this by running ‘mysqlbinlog’ on the binary log), the slave’s relay log is corrupted (you can check this by running ‘mysqlbinlog’ on the relay log), a network problem, or a bug in the master’s or slave’s MySQL code. If you want to check the master’s binary log or slave’s relay log, you will be able to know their names by issuing ‘SHOW SLAVE STATUS’ on this slave. Skip\_Counter: 0 Exec\_Master\_Log\_Pos: 158467795 Relay\_Log\_Space: 43352744 Until\_Condition: None Until\_Log\_File: Until\_Log\_Pos: 0 Master\_SSL\_Allowed: No Master\_SSL\_CA\_File: Master\_SSL\_CA\_Path: Master\_SSL\_Cert: Master\_SSL\_Cipher: Master\_SSL\_Key: Seconds\_Behind\_Master: NULL I try to check the relay log and found something really weird as below: Quote: > [@](#): > > /_!40019 SET @@session.max\_insert\_delayed\_threads=0_/; > /_!50003 SET @OLD\_COMPLETION\_TYPE=@@COMPLETION\_TYPE,COMPLETION\_TYPE=0_/; > DELIMITER /_!_/; > > # at 4 > > #130408 23:57:03 server id 3 end\_log\_pos 98 Start: binlog v 4, server v 5.0.77-log created 130408 23:57:03 > > # at 98 > > #700101 7:30:00 server id 1 end\_log\_pos 0 Rotate to mysql-bin.000070 pos: 158467505 > > # at 141 > > #130402 1:19:28 server id 1 end\_log\_pos 0 Start: binlog v 4, server v 5.5.28-log created 130402 1:19:28 > > # at 244 > > #130408 7:04:36 server id 1 end\_log\_pos 158467626 Query thread\_id=48927 exec\_time=0 error\_code=0 > use mysql/_!_/; > SET TIMESTAMP=1365375876/_!_/; > SET @@session.foreign\_key\_checks=1, @@session.sql\_auto\_is\_null=0, @@session.unique\_checks=1/_!_/; > SET @@session.sql\_mode=0/_!_/; > /_!\C latin1 //!_/; > SET @@session.character\_set\_client=8,@@session.collation\_connection=8,@@session.collation\_server=8/_!_/; > DROP TABLE IF EXISTS `yongger2` /\* generated by server _/ > /_!\*/; > > # at 365 > > #130408 7:04:36 server id 1 end\_log\_pos 158467726 Query thread\_id=48927 exec\_time=0 error\_code=0 > SET TIMESTAMP=1365375876/_!_/; > create table yongger2(data LONGBLOB) > /_!_/; > > # at 465 > > #130408 7:04:38 server id 1 end\_log\_pos 158467795 Query thread\_id=48927 exec\_time=0 error\_code=0 > SET TIMESTAMP=1365375878/_!_/; > BEGIN > /_!_/; > ERROR: Error in Log\_event::read\_log\_event(): ‘Found invalid event in binary log’, data\_len: 49, event\_type: 19 > Could not read entry at offset 534:Error in log format or read error > DELIMITER ; > > # End of log file > > ROLLBACK /\* added by mysqlbinlog _/; > /_!50003 SET COMPLETION\_TYPE=@OLD\_COMPLETION\_TYPE\*/; > [root@csbackup teckkongtbj]# mysqlbinlog teckkongtbj-relay-bin.2828242 > /_!40019 SET @@session.max\_insert\_delayed\_threads=0_/; > /_!50003 SET @OLD\_COMPLETION\_TYPE=@@COMPLETION\_TYPE,COMPLETION\_TYPE=0_/; > DELIMITER /_!_/; > mysqlbinlog: File ‘teckkongtbj-relay-bin.2828242’ not found (Errcode: 2) > DELIMITER ; > > # End of log file > > ROLLBACK /\* added by mysqlbinlog _/; > /_!50003 SET COMPLETION\_TYPE=@OLD\_COMPLETION\_TYPE\*/; What is yongger2? I never seen this before in my database, and i try to check percona master bin log, i can see such query too. However the Percona Slave is working just fine. I have other Percona Master and Slave server which is different from this 2, and i try to do replication to the same standard mysql server and same error came out too. Thanks for help.