# multiple slaves error: bogus data in log event

**URL:** <https://forums.percona.com/t/multiple-slaves-error-bogus-data-in-log-event/5368>\
**Category:** General Questions\
**Created:** [January 25, 2017, 12:11pm UTC](https://forums.percona.com/t/multiple-slaves-error-bogus-data-in-log-event/5368 "2017-01-25T12:11:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcanete](https://avatars.discourse-cdn.com/v4/letter/j/2bfe46/32.png) [@jcanete](https://forums.percona.com/u/jcanete)\
**Post date:** [January 25, 2017, 12:11pm UTC](https://forums.percona.com/t/multiple-slaves-error-bogus-data-in-log-event/5368/1 "2017-01-25T12:11:22Z")

</div>

hello, we have one master and two slaves and as soon as the slaves start to replicate, we get this error in one slave only (the other keeps running):

Last\_IO\_Error: Got fatal error 1236 from master when reading data from binary log: ‘bogus data in log event; the first event ‘mysql-bin.000002’ at 211200498, the last event read from ‘/var/lib/mysql/binlog/mysql-bin.000002’ at 211359690, the last byte read from ‘/var/lib/mysql/binlog/mysql-bin.000002’ at 211359709.’

If we start the slave with the error, it keeps working until the slaves are up-to-date again and one of them gets the error. So we think that the issue is in some way related to the binlog concurrence reading by the slave server I/O thread. If the slaves are not reading from the same position of the binlog (no concurrence readings), the error does not happen.

We can prevent this error in three ways:

- having only one slave (not an option, we need two of them)
- setting slave\_compressed\_protocol=1 (not an option, too much cpu usage)
- change the sync\_binlog value to off (not an option, we cannot lose transactions)

mysql-community-server-5.7.12-1  
Red Hat Enterprise Linux Server release 6.5 (Santiago)

- GTID is enabled (this is something that we need too)

Any ideas to fix this issue?  
Regards.

---

<div class="post-metadata">

**Author:** ![jcanete](https://avatars.discourse-cdn.com/v4/letter/j/2bfe46/32.png) [@jcanete](https://forums.percona.com/u/jcanete)\
**Post date:** [February 1, 2017, 8:40am UTC](https://forums.percona.com/t/multiple-slaves-error-bogus-data-in-log-event/5368/2 "2017-02-01T08:40:01Z")

</div>

Any help would be appreciated. Thanks.

---

<div class="post-metadata">

**Author:** ![mirfan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mirfan/32/16890_2.png) [@mirfan](https://forums.percona.com/u/mirfan)\
**Post date:** [April 1, 2017, 2:37am UTC](https://forums.percona.com/t/multiple-slaves-error-bogus-data-in-log-event/5368/3 "2017-04-01T02:37:47Z")

</div>

Make sure you have innodb\_flush\_log\_at\_trx\_commit & sync\_binlog set to 1 on master. Do you have crash slave featured enabled ([url][https://www.percona.com/blog/2013/09/13/enabling-crash-safe-slaves-with-mysql-5-6/[/url]](https://www.percona.com/blog/2013/09/13/enabling-crash-safe-slaves-with-mysql-5-6/%5B/url%5D)) ? It would be better to review master/slave(s) my.cnf