Hello *,

I'm doing a master/slave setup in 2 OpenVZ hosts both with debian 7 and MariaDB 10.0 from the offical repository.

The problem is that the slave sometimes bails out with the following error message:

Got fatal error 1236 from master when reading data from binary log: 'binlog truncated in the middle of event; consider out of disk space on master; the first event 'mysql-bin.000073' at 33590521, the last event read from 'mysql-bin.000073' at 39362449, the last byte read from 'mysql-bin.000073' at 39362560.'

Okay, no problem I start the replication with "START SLAVE" but the next error occurs within 5 minutes or so:

Got fatal error 1236 from master when reading data from binary log: 'binlog truncated in the middle of event; consider out of disk space on master; the first event 'mysql-bin.000073' at 39362449, the last event read from 'mysql-bin.000073' at 48667806, the last byte read from 'mysql-bin.000073' at 48668672.'

Sometimes it runs so for a week sometimes it fails 3 times within 15 minutes. It seems that the slave read some data and but the master havn't finished writing the data to the binlog. That should be impossible.

So after starting the slave again everything is fine again. I can start the replication again with "START SLAVE" and everything is fine again for some times until the error appears again.

And it's not that I'm running out of disc space I'm running here out of ideas. B-)

Some other info:

[mysqld] ... binlog-ignore-db = mysql binlog-ignore-db = test server_id = 10 log_bin = mysql-bin read_only = yes sync_binlog = 1 binlog_format = MIXED expire_logs_days = 14 max_allowed_packet = 1047527424

Any other "esoteric" ideas?