Hi all, I am having some issues with my replication setup which I have narrowed down to being a problem on the master, more specifically an issue with the binlog when using a trigger.
I have a trigger on one of my tables that archives an entry before deleting it: DELIMITER // CREATE TRIGGER d_adi_95_long BEFORE DELETE ON adi_95_long FOR EACH ROW BEGIN INSERT INTO D_adi_95_long select *,NULL,NOW() from adi_95_long WHERE adi_id=OLD.adi_id; END; // DELIMITER ; The table D_adi_95_long is identical to adi_95_long except the last 2 columns, one being a auto_increment field, the other a timestamp. When I delete from adi_95_long, the trigger is executed but I get this line in my binlog (which I assume creates the problem on the slaves): ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 173056, event_type: 73 I have the exact same scenario for various other tables and have no issues there, this is by far the table with the most columns (209) however. When I started researching this by googling the errors I was getting in the slaves error log: 081230 12:20:25 [ERROR] Error reading packet from server: error reading log entry ( server_errno=1236) 081230 12:20:25 [ERROR] Got fatal error 1236: 'error reading log entry' from master when reading data from binary log I found a post suggesting this was a max_allowed_packet (currently 256M) issue on the master, which I could not confirm. It seems possible though as I am having this issues with the largest of tables only. What is the unit for data_len: 173056 in above binlog entry? Any other ideas are appreciated as well as I am not sure what to do here. Thanks Olaf ----------------------------------------- Confidentiality Notice: The following mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. The recipient is responsible to maintain the confidentiality of this information and to use the information only for authorized purposes. If you are not the intended recipient (or authorized to receive information for the intended recipient), you are hereby notified that any review, use, disclosure, distribution, copying, printing, or action taken in reliance on the contents of this e-mail is strictly prohibited. If you have received this communication in error, please notify us immediately by reply e-mail and destroy all copies of the original message. Thank you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
