Bug #437 Replication Problem
Submitted: 16 May 2003 8:05 Modified: 2 Feb 2004 6:29
Reporter: suman aluru Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:4.0.12 OS:Linux (Redhat Linux8.0)
Assigned to: Assigned Account CPU Architecture:Any

[16 May 2003 8:05] suman aluru
030516 09:50:49  mysqld started
030516  9:50:50  InnoDB: Started
/usr/sbin/mysqld: ready for connections.
Version: '4.0.12'  socket: '/var/lib/mysql/mysql.sock'  port: 3306
030516  9:50:50  Error in Log_event::read_log_event(): 'Event too big', data_len=741553966,event_type=49
030516  9:50:50  Error reading relay log event: slave SQL thread aborted because of I/O error
030516  9:50:50  Could not parse log event entry, check the master for binlog corruption
This may also be a network problem, or just a bug in the master or slave code.
030516  9:50:50  Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db01p-bin.007' position 1801

How to repeat:
[21 May 2003 6:37] Guilhem Bichot
Hi Suman,

Few days ago I sent you an email. In case it got lost, here it is again :
Could you please put an archive containing 'db01p-bin.007', and your master's and slave's .err files, on ftp://support.mysql.com/pub/mysql/secret/ ?
Please zip it.
Please save all the binlogs from db01p-bin.001 to .007, in case we need them for analysis. 
Do not delete them. These files are extremely important.
If the total size of .001 to .007 does not exceed a few MB when zipped, you may put the total archive (.001 to .007) on the ftp place.

Thanks a lot.

For technical support contracts, visit https://order.mysql.com/?ref=mgbi
Are you MySQL certified? visit http://www.mysql.com/certification/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Mr. Guilhem Bichot <guilhem@mysql.com>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Full-Time Software Developer
/_/  /_/\_, /___/\___\_\___/   Bordeaux, France
       <___/   www.mysql.com
[2 Feb 2004 6:29] Guilhem Bichot
Maybe we'll get more feedback from BUG#2556 which looks like a duplicate.