MySQL master slave replication

MySQL

I had MySQL master/slave replication working properly but suddenly replication stopped and accidentally someone has changed mysql.binxxx file in salve so I am getting this error

ERROR: 'Got fatal error 1236'.

So I checked latest mysql.bin and log poss from master and changed in slave so replication started but now again new mysql.binxxx created in server so again I am getting fatal error. Is there any fix solution for this without any data loss.

Best Answer

If your instance is not that big, your best bet would be to recreate your slave from scratch.

You won't be losing data since from what I understand, your master is fine.

Related Solutions

Thesql replication deadlock slave stopped

This query fails on slave: 'insert into archieved(eid,at,rtime,scode) select id,at,avg(rtime),scode from tstatus where date(at)="2011-10-29" group by id'

You report a strange Error_code: 0, but try to run this query on slave? When it run succesfully then run as root:

SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;
SLAVE START;

Mysql – Broken thesql replication on slave server (error 1236)

I believe the log file and position need to be specified with the host.

Try:

CHANGE MASTER TO MASTER_HOST='192.168.1.105', MASTER_USER='slaveuser', MASTER_PASSWORD='mypassword', MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=107;

Best Answer

Related Solutions

Thesql replication deadlock slave stopped

Mysql – Broken thesql replication on slave server (error 1236)

Related Question