Hello, I am having replication troubles with 4.0.15. Some info:
mysql> show slave status; | www.x.com | replicon | 3306 | 60 | ns1-bin.001 | 16958428 | linux-relay-bin.011 | 623915 | ns1-bin.001 | Yes | No | | | 0 | 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. | 0 | 8147397 | 9437494 The server bin log is fine. The slave bin log gives the error: # mysqlbinlog linux-relay-bin.011 >m ERROR: Error in Log_event::read_log_event(): 'Event too big', data_len: 1701345056, event_type: 61 ERROR: Could not read entry at offset 622931 : Error in log format or read error Some google searches show this was noticed in 4.0.5 as well. I'm not specifying max_binlog_size on the master or server. I am not specifying max_allowed_packet on the master. I have not set max_packet_size either. I note that my bin logs are only 9MB on the slave. I'm currently upgrading to 4.0.18 but unless I missed it I don't see this fixed in the changelogs. Anyone have any recommendations on how to ensure this doesn't happen again? Thanks! -- VoIP SIP:[EMAIL PROTECTED] Free calendar client and server - works with Exchange/Outlook Now with TV-Listing Schedules for 13 countries! http://www.ScheduleWorld.com/ http://www.ScheduleWorld.com/sw/ScheduleWorld.jnlp (JWS) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
