Our master suffered a power failure. When fixed we brought up its only slave and found that it wouldn't replicate. The error log revealed that the slave was requesting replication from an impossible position:
Slave SQL thread initialized, starting replication in log 'dbm-bin.041' at position 117415283, relay log './dbs1-relay-bin.016' position: 117415850 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'dbm-bin.041' at position 117415283 Error reading packet from server: Client requested master to start replication from impossible position (server_errno=1236) Got fatal error 1236: 'Client requested master to start replication from impossible position' from master when reading data from binary log Slave I/O thread exiting, read up to log 'dbm-bin.041', position 117415283 Master status: mysql> show master status; +-------------+----------+--------------+------------------+ | File | Position | Binlog_do_db | Binlog_ignore_db | +-------------+----------+--------------+------------------+ | dbm-bin.043 | 89536436 | | | +-------------+----------+--------------+------------------+ I'm guessing the slave is out of sync because the master wasn't able to flush its data to disk before failing. Is it possible to recover from this situation -- perhaps by modifying master.info and relay-log.info? Or should I start over with a new snapshot of the master? Thanks, Paul -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
