Hi,
this weekend during my backup the harddisk ran full and the replication stopped.
For me it looks like i wont be able to recover from this,
so is there a way to start a new slave without stopping the master?
If there is still a way I would be glad, but I cant risk any dataloss on the slave side.
MY mysql Version ist 5.1.50-log SUSE MySQL RPM
The setup is a simple master->slave replication with statement based replication.
The first error looked like this
------------------------------------------------------------------------
Last_IO_Errno: 1236
Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'
Last_SQL_Errno: 1064
Last_SQL_Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
1 row in set (0.00 sec)
------------------------------------------------------------------------
than I skipped one error and now i get
------------------------------------------------------------------------
Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'
Last_SQL_Errno: 1594
Last_SQL_Error: Relay log read failure: 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.
------------------------------------------------------------------------
thnx for your help
this weekend during my backup the harddisk ran full and the replication stopped.
For me it looks like i wont be able to recover from this,
so is there a way to start a new slave without stopping the master?
If there is still a way I would be glad, but I cant risk any dataloss on the slave side.
MY mysql Version ist 5.1.50-log SUSE MySQL RPM
The setup is a simple master->slave replication with statement based replication.
The first error looked like this
------------------------------------------------------------------------
Last_IO_Errno: 1236
Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'
Last_SQL_Errno: 1064
Last_SQL_Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
1 row in set (0.00 sec)
------------------------------------------------------------------------
than I skipped one error and now i get
------------------------------------------------------------------------
Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'
Last_SQL_Errno: 1594
Last_SQL_Error: Relay log read failure: 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.
------------------------------------------------------------------------
thnx for your help