Bug #11407 After the master machine had crashed, got fatal error 1236
Submitted: 17 Jun 2005 8:25 Modified: 21 Jun 2005 3:36
Reporter: Dominique Corfa Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.0.15-max-debug OS:Windows (Windows server 2003)
Assigned to: CPU Architecture:Any

[17 Jun 2005 8:25] Dominique Corfa
Description:
One master and one slave : A->B.
The master's machine crashed and then restart, and the master open a new N bin log. The slave didn't stop and reconnect to the master BUT the log position  is beyond the master N-1 log file. So the Slave I/O thread stop when receiving the following error from the master.

MySql: ready for connections.
Version: '4.0.15-max-debug'  socket: ''  port: 3306
050616  3:09:08  Slave I/O thread: connected to master 'repl@euw0800035.eu.verio.net:3306',  replication started in log 'euw0800035-bin.019' at position 44493632
050616  3:09:08  Error reading packet from server: Client requested master to start replication from impossible position (server_errno=1236)
050616  3:09:08  Got fatal error 1236: 'Client requested master to start replication from impossible position' from master when reading data from binary log
050616  3:09:08  Slave I/O thread exiting, read up to log 'euw0800035-bin.019', position 44493632
050616 10:50:04  Slave I/O thread: connected to master 'repl@euw0800035.eu.verio.net:3306',  replication started in log 'euw0800035-bin.019' at position 44482710

How to repeat:
un-plug the master.

Suggested fix:
[21 Jun 2005 3:36] MySQL Verification Team
I was unable to repeat the issue reported with current server
released 4.0.24.