Re: Replication error 1236
See Thread at: http://www.techienuggets.com/Detail?tx=46643 Posted on behalf of a User HI, first check the error log and find the position where the replication was terminated.Now run the mysqlbinlog utility on the binarylogs file. Now when you run the query will get the text format as a result.serch for the position and see as to which query was ran on that position.check if that qurey ran on the slave before bcoz we dont need a duplication of thr query.If not plz run the query on the slave.Stop/start the slave.You sholud get the Slave back to SYNC. Anup In Response To: Hi All, Once a week or so I get the following error: 080801 8:18:35 [ERROR] Error reading packet from server: error reading log entry ( server_errno=1236) 080801 8:18:35 [ERROR] Got fatal error 1236: 'error reading log entry' from master when reading data from binary log Stopping the slave and restart at its current postion does not help here (the same error happens again with next entry in bin log), the only way I know how to fix this is to flush the logs and restart the slave with the new log file (changes in between are manually synched). I would appreciate any pointers about where to start looking for the problem. E.g. is the bin log file corrupt? And if so why does this happen so often 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/[EMAIL PROTECTED]
Replication error 1236
Hi All, Once a week or so I get the following error: 080801 8:18:35 [ERROR] Error reading packet from server: error reading log entry ( server_errno=1236) 080801 8:18:35 [ERROR] Got fatal error 1236: 'error reading log entry' from master when reading data from binary log Stopping the slave and restart at its current postion does not help here (the same error happens again with next entry in bin log), the only way I know how to fix this is to flush the logs and restart the slave with the new log file (changes in between are manually synched). I would appreciate any pointers about where to start looking for the problem. E.g. is the bin log file corrupt? And if so why does this happen so often 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/[EMAIL PROTECTED]
Replication error (1236 - impossible position on slave)
Hi, We have 2 MySQL 4.0.16 with replication enabled (M -> S), only InnoDB tables. We're getting "Error reading packet from server: Client requested master to start replication from impossible position (server_errno=1236)" in the slave. The master server had a problem... when it came back (with success) the log have: "031210 15:19:24 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 3 4169000545 InnoDB: Doing recovery: scanned up to log sequence number 3 4171205097 031210 15:19:25 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 45866, file name ./SV07-bin.008 031210 15:19:43 InnoDB: Flushing modified pages from the buffer pool... 031210 15:19:51 InnoDB: Started" But in the slave log: "031210 17:02:36 Slave: connected to master '[EMAIL PROTECTED]:xxx',replication resumed in log 'SV07-bin.008' at position 45866 031210 17:02:36 Error reading packet from server: Client requested master to start replication from impossible position (server_errno=1236) 031210 17:02:36 Got fatal error 1236: 'Client requested master to start replication from impossible position' from master when reading data from binary log 031210 17:02:36 Slave I/O thread exiting, read up to log 'SV07-bin.008', position 45866" With "show master status" (on master) I get: File = SV07-bin.009 Position = 456371766 And with "show slave status" (on slave) I get: Master_log_file = SV07-bin.008 Read_master_log_pos = 45866 Relay_log_file = SV08-relay-bin.011 Relay_log_pos = 458600084 Relay_master_log = SV07-bin.008 Slave_io_running = no Slave_sql_running = yes Exec_master_log_pos = 45866 Relay_log_space = 458600084 Is SV07-bin.008 corrupted? How can I debug? Thanks, Eduardo -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
