Comments on: MySQL fatal error 1236

By: Suresh

Suresh — Wed, 12 Oct 2011 06:33:35 +0000

Thanks a lot !! saved lot of time for me.

By: Patrick Dorion

Patrick Dorion — Wed, 03 Aug 2011 22:10:21 +0000

This is great and I also lost a few moments off of my life with this one. It would, however, have saved me even more time if it was posted on the MySQL Community Server Community pages.

By: Leslie

Leslie — Wed, 25 May 2011 16:44:12 +0000

Awesome post, and comments. Definitely saved me a ton of time (when I had *none* to spare). Thanks to all who contributed.

By: Charlie Roche

Charlie Roche — Mon, 02 May 2011 17:06:24 +0000

Update to the previous post. Here's a link to the MySQL documentation that explains this - see the "Note" at the end of this page. How Servers Evaluate Replication Filtering Rules

By: Charlie Roche

Charlie Roche — Mon, 02 May 2011 16:58:22 +0000

Hi. I had this problem too and there’s another reason this error occurs. Case sensitivity of the table names. I found that it’s best to have these global settings the same on the master and slave. Try this on both to see if they are different.

show variables where
Variable_name = ‘lower_case_table_names’ OR
Variable_name=’lower_case_file_system’;

These should be the same on both master and slave.

By: Patricia

Patricia — Wed, 04 Nov 2009 18:14:20 +0000

This page helped (and especially the comments).

My error was:
ERROR] Got fatal error 1236: ‘Client requested master to start replication from impossible position’ from master when reading data from binary log

My fix on the slave was to be:
LOAD DATA FROM MASTER;

However I first had to grant extra privileges to my account from the master:
grant reload, replication client on *.* to ‘repl-user’@'server-name’

By: Anon

Anon — Mon, 28 Sep 2009 18:18:57 +0000

A HUGE thank you to Burkhart and Doug!!!

Came in today and there was: Could not find first log file name in binary log index file ( server_errno=1236)

It popped up after a master reboot over the weekend. Checked the log file and it was indeed at the end. Set replication to the next file at first position (which was also 4 )and everything came right back up.

14 hours or so saved by not re-replicating from scratch.

By: doug

doug — Fri, 29 May 2009 07:38:57 +0000

@Dhananjay: I have seen this happen as well. Thanks for the info.

By: Dhananjay

Dhananjay — Fri, 29 May 2009 07:28:26 +0000

Hi,i too faced similar problem.In my case the replication was broken because of ‘max_allowed_packet’.A big query was logged in the binary log and the same was not able to communicate with slave.By default the packet size will be 1MB.I have increased the ‘max_allowed_packet’ to 16M on both master and slave.
Steps: stop slave,change master,start slave.

Note:When you’re using CHANGE MASTER TO to set start position for the slave you’re specifying position for SQL thread and so you should use Relay_Master_Log_File:Exec_Master_Log_Pos. Otherwise you’re going to ruin your replication.

By: doug

doug — Wed, 20 May 2009 16:55:47 +0000

@Halfasleep: Thanks for the tip. What version of MySQL are you using? Maybe that makes a difference.