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]
Re: Replication broken - fatal error 1236: 'error reading log entry'
On Wed, Jul 18, 2007 at 06:13:10PM -0400, I wrote: This afternoon, both slaves stopped at the same place, with the same error: 070718 17:28:00 [ERROR] Error reading packet from server: error reading log entry ( server_errno=1236) 070718 17:28:00 [ERROR] Got fatal error 1236: 'error reading log entry' from master when reading data from binary log 070718 17:28:00 [Note] Slave I/O thread exiting, read up to log 'hlgbinlog-oil.15', position 139702230 It turns out that this is due to a large query and max_allowed_packet being too small for that query, on the *master*. If max_allowed_packet on the slave is too small, you'll get an error message that directly tells you max_allowed_packet is too small; but if it's too small on the master, you'll get this cryptic message in the slave's error log, and nothing at all on the master's error log. -- Cos -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Replication broken - fatal error 1236: 'error reading log entry'
MySQL 5.0.27 from RPM, on Redhat EL4. One master, two slaves, one database. Slaves have been up for 5 days. This afternoon, both slaves stopped at the same place, with the same error: 070718 17:28:00 [Note] Slave SQL thread initialized, starting replication in log 'hlgbinlog-oil.15' at position 138655868, relay log '/data/mysql/logs/soda-relay.25' position: 138656009 070718 17:28:00 [Note] Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'hlgbinlog-oil.15' at position 139702230 070718 17:28:00 [ERROR] Error reading packet from server: error reading log entry ( server_errno=1236) 070718 17:28:00 [ERROR] Got fatal error 1236: 'error reading log entry' from master when reading data from binary log 070718 17:28:00 [Note] Slave I/O thread exiting, read up to log 'hlgbinlog-oil.15', position 139702230 If I try to stop and restart the slave threads, or restart mysql, it just logs the same error again. The relay log ends there. The last query in the relay log, which matches the query in the master's binlog at position 139702230, is large insert statement. I tried grep'ing the query out of the master's binlog with mysqlbinlog, copying it to one of the slaves, and running it there (mysql -ufoo -p query.sql) and it worked, so the query seems fine, though perhaps its large size is related to the problem. Any suggestions on how to re-start replication, and how to avoid this? -- Cos -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Slave I/O thread dies, fatal error 1236
matt ryan wrote: Tobias Asplund wrote: On Tue, 7 Sep 2004, matt ryan wrote: I forgot, did you have multiple slaves on multiple machines? If so, do they have identical hardware/drivers? Multiple slaves on same machine, one works fine Do You tried to distribute replication to other machines? Is it option to You? Remigiusz -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Slave I/O thread dies, fatal error 1236
Remigiusz Sokoowski wrote: matt ryan wrote: Tobias Asplund wrote: On Tue, 7 Sep 2004, matt ryan wrote: I forgot, did you have multiple slaves on multiple machines? If so, do they have identical hardware/drivers? Multiple slaves on same machine, one works fine Do You tried to distribute replication to other machines? Is it option to You? Remigiusz I will setup a separate server as a slave and see if it works, that would narrow it down to the master being the problem -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Slave I/O thread dies, fatal error 1236
Still have not got this fixed, I'm all out of idea's, the slave has been reloaded again today gerald_clark wrote: We have no idea what you are running, or what you are running it on. matt ryan wrote: 040901 18:36:21 Error reading packet from server: binlog truncated in the middle of event (server_errno=1236) 040901 18:36:21 Got fatal error 1236: 'binlog truncated in the middle of event' from master when reading data from binary log 040901 18:36:21 Slave I/O thread exiting, read up to log 'FINANCE-bin.186', position 7517914 2 slaves on one box both masters have identical config one slave will not stay running for more than an hour, it seems that it will run until it catches up with the master, then it dies. Any sugestions? All servers have plenty of free drive space Oops sorry windows 2000, mysql 4.0.20d here's the config on the affected server, it is identical to the server that works fine, except for the port number and base/data dir's it's interesting to note, that if I wait a few minutes after the thread dies, and issue start slave it'll usually start right up and run until it's caught up to the master server again. Matt skip-locking set-variable= key_buffer_size=1500M set-variable=join_buffer_size=512M set-variable= max_allowed_packet=300M set-variable= table_cache=512 set-variable=delay_key_write=ALL set-variable= sort_buffer_size=256M set-variable= record_buffer=300M set-variable= thread_cache=8 set-variable=myisam_sort_buffer_size=256M myisam-recover=BACKUP,FORCE set-variable=read_buffer_size=300M set-variable=interactive_timeout=7200 set-variable=wait_timeout=7200 set-variable=thread_concurrency=4 server-id=5 #log-bin master-host=192.168.1.168 master-port=3306 master-user=repl master-password=Daredevil22 master-connect-retry=60 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Slave I/O thread dies, fatal error 1236
On Tue, 7 Sep 2004, matt ryan wrote: Still have not got this fixed, I'm all out of idea's, the slave has been reloaded again today I forgot, did you have multiple slaves on multiple machines? If so, do they have identical hardware/drivers? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Slave I/O thread dies, fatal error 1236
Tobias Asplund wrote: On Tue, 7 Sep 2004, matt ryan wrote: I forgot, did you have multiple slaves on multiple machines? If so, do they have identical hardware/drivers? Multiple slaves on same machine, one works fine -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Slave I/O thread dies, fatal error 1236
040901 18:36:21 Error reading packet from server: binlog truncated in the middle of event (server_errno=1236) 040901 18:36:21 Got fatal error 1236: 'binlog truncated in the middle of event' from master when reading data from binary log 040901 18:36:21 Slave I/O thread exiting, read up to log 'FINANCE-bin.186', position 7517914 2 slaves on one box both masters have identical config one slave will not stay running for more than an hour, it seems that it will run until it catches up with the master, then it dies. Any sugestions? All servers have plenty of free drive space -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Slave I/O thread dies, fatal error 1236
We have no idea what you are running, or what you are running it on. matt ryan wrote: 040901 18:36:21 Error reading packet from server: binlog truncated in the middle of event (server_errno=1236) 040901 18:36:21 Got fatal error 1236: 'binlog truncated in the middle of event' from master when reading data from binary log 040901 18:36:21 Slave I/O thread exiting, read up to log 'FINANCE-bin.186', position 7517914 2 slaves on one box both masters have identical config one slave will not stay running for more than an hour, it seems that it will run until it catches up with the master, then it dies. Any sugestions? All servers have plenty of free drive space -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Slave I/O thread dies, fatal error 1236
gerald_clark wrote: We have no idea what you are running, or what you are running it on. matt ryan wrote: 040901 18:36:21 Error reading packet from server: binlog truncated in the middle of event (server_errno=1236) 040901 18:36:21 Got fatal error 1236: 'binlog truncated in the middle of event' from master when reading data from binary log 040901 18:36:21 Slave I/O thread exiting, read up to log 'FINANCE-bin.186', position 7517914 2 slaves on one box both masters have identical config one slave will not stay running for more than an hour, it seems that it will run until it catches up with the master, then it dies. Any sugestions? All servers have plenty of free drive space Oops sorry windows 2000, mysql 4.0.20d here's the config on the affected server, it is identical to the server that works fine, except for the port number and base/data dir's it's interesting to note, that if I wait a few minutes after the thread dies, and issue start slave it'll usually start right up and run until it's caught up to the master server again. Matt skip-locking set-variable= key_buffer_size=1500M set-variable=join_buffer_size=512M set-variable= max_allowed_packet=300M set-variable= table_cache=512 set-variable=delay_key_write=ALL set-variable= sort_buffer_size=256M set-variable= record_buffer=300M set-variable= thread_cache=8 set-variable=myisam_sort_buffer_size=256M myisam-recover=BACKUP,FORCE set-variable=read_buffer_size=300M set-variable=interactive_timeout=7200 set-variable=wait_timeout=7200 set-variable=thread_concurrency=4 server-id=5 #log-bin master-host=192.168.1.168 master-port=3306 master-user=repl master-password=Daredevil22 master-connect-retry=60 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Fatal error 1236 (replication)
Our master suffered a power failure. When fixed we brought up its only slave and found that it wouldn't replicate. The error log revealed that the slave was requesting replication from an impossible position: Slave SQL thread initialized, starting replication in log 'dbm-bin.041' at position 117415283, relay log './dbs1-relay-bin.016' position: 117415850 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'dbm-bin.041' at position 117415283 Error reading packet from server: Client requested master to start replication from impossible position (server_errno=1236) Got fatal error 1236: 'Client requested master to start replication from impossible position' from master when reading data from binary log Slave I/O thread exiting, read up to log 'dbm-bin.041', position 117415283 Master status: mysql show master status; +-+--+--+--+ | File| Position | Binlog_do_db | Binlog_ignore_db | +-+--+--+--+ | dbm-bin.043 | 89536436 | | | +-+--+--+--+ I'm guessing the slave is out of sync because the master wasn't able to flush its data to disk before failing. Is it possible to recover from this situation -- perhaps by modifying master.info and relay-log.info? Or should I start over with a new snapshot of the master? Thanks, Paul -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Error 1236 corrupt binlog on master
I have been using the mysqlbinlog to investigate the 'saturn2-bin.051' binlog file.. I have come to pinpoint the problem position in the binlog, but don't know how i can bypass the corrupted segment. Please help. Thanks Arvind. -Original Message- From: Arvind Gangal [mailto:[EMAIL PROTECTED] Sent: 24 March 2004 21:17 To: '[EMAIL PROTECTED]' Subject: Error 1236 corrupt binlog on master Hello Gurus, Anyone have any ideas as to how I should handle a case of the following error? 040324 21:02:05 Slave I/O thread: connected to master mailto:'[EMAIL PROTECTED]:3306' '[EMAIL PROTECTED]:3306', replication started in log 'saturn2-bin.051' at position 442744915 040324 21:02:05 Error in Log_event::read_log_event(): 'read error', data_len=657471024,event_type=61 040324 21:02:05 Slave SQL thread: I/O error reading event(errno: -1 cur_log-error: 1723122) 040324 21:02:05 Error reading relay log event: Aborting slave SQL thread because of partial event read 040324 21:02:05 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. 040324 21:02:05 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with SLAVE START. We stopped at log 'satur n2-bin.051' position 442744915 040324 21:02:05 Error reading packet from server: binlog truncated in the middle of event (server_errno=1236) 040324 21:02:05 Got fatal error 1236: 'binlog truncated in the middle of event' from master when reading data from binary log 040324 21:02:05 Slave I/O thread exiting, read up to log 'saturn2-bin.051', position 442744915 Replication seems to have stopped at that point and the slave keeps trying to connect and dies at with that error. I think that the binlog file 'saturn2-bin.051' on master has got courrupted. Is there any way i can start after the point of corruption in the binary file? Thanks, Arvind Arvind Gangal Senior Analyst Programmer address: 4 Buckingham Gate, London SW1E 6JP tel: +44 (0)20 7802 4306 fax: +44 (0)20 7802 9302 mob: 07734938242 email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] internet: http://www.lastminute.com/ http://www.lastminute.com do something lastminute.com This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Error 1236 corrupt binlog on master
Arvind Gangal wrote: I have been using the mysqlbinlog to investigate the 'saturn2-bin.051' binlog file.. I have come to pinpoint the problem position in the binlog, but don't know how i can bypass the corrupted segment. This is a bit tricky. Open the binlog in a hex editor, and go to the last good offset (printed in the comments). At offset 9 from there you will find a 4-byte integer in little-endian format. That is the length of the last good event. Add it to the last good offset. Now you are at the corrupted event. This is where the science ends and the black magic begins. Again, at offset 9 you will find what is supposed to be the event length, and at offset 4 you will find 1 byte event type code. The codes are listed in sql/log_event.h in the enum Log_event_type. Figure out where the next good event really starts, and fix up the type to be something innocent (eg. INTVAR_EVENT) + the length so that you will jump to the next event. As a word of caution, you may not find much useful data after the corrupted event, but if it is at the end of file, you can manually put a ROTATE_EVENT to instruct the slave to switch to the next log. However, if this is a practical problem, and not just a study of how things work, I would suggest reporting the bug ( if this happened with the latest version), and resetting the replication. -- Sasha Pachev Create online surveys at http://www.surveyz.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Error 1236 corrupt binlog on master
Hello Gurus, Anyone have any ideas as to how I should handle a case of the following error? 040324 21:02:05 Slave I/O thread: connected to master mailto:'[EMAIL PROTECTED]:3306' '[EMAIL PROTECTED]:3306', replication started in log 'saturn2-bin.051' at position 442744915 040324 21:02:05 Error in Log_event::read_log_event(): 'read error', data_len=657471024,event_type=61 040324 21:02:05 Slave SQL thread: I/O error reading event(errno: -1 cur_log-error: 1723122) 040324 21:02:05 Error reading relay log event: Aborting slave SQL thread because of partial event read 040324 21:02:05 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. 040324 21:02:05 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with SLAVE START. We stopped at log 'satur n2-bin.051' position 442744915 040324 21:02:05 Error reading packet from server: binlog truncated in the middle of event (server_errno=1236) 040324 21:02:05 Got fatal error 1236: 'binlog truncated in the middle of event' from master when reading data from binary log 040324 21:02:05 Slave I/O thread exiting, read up to log 'saturn2-bin.051', position 442744915 Replication seems to have stopped at that point and the slave keeps trying to connect and dies at with that error. I think that the binlog file 'saturn2-bin.051' on master has got courrupted. Is there any way i can start after the point of corruption in the binary file? Thanks, Arvind Arvind Gangal Senior Analyst Programmer address: 4 Buckingham Gate, London SW1E 6JP tel: +44 (0)20 7802 4306 fax: +44 (0)20 7802 9302 mob: 07734938242 email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] internet: http://www.lastminute.com/ http://www.lastminute.com do something lastminute.com This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk
Request help with error 1236
Hello all, I have a simple MySQL replication system setup with a single master and a single slave. The slave is running 4.0.16-standard and the master is running 4.0.16-standard-log. On an (almost) daily basis, I get this error on my slave: 031216 9:55:44 Error reading packet from server: log event entry exceeded max_allowed_packet; Increase max_allowed_packet on master (server_errno=1236) 031216 9:55:44 Got fatal error 1236: 'log event entry exceeded max_allowed_packet; Increase max_allowed_packet on master' from master when reading data from binary log 031216 9:55:44 Slave I/O thread exiting, read up to log 'el-bin.001', position 589631188 Note, this does not happen at the same time during the day and it does not happen every day. I know this is not a problem with max_allowed_packet because I have set both the master and slave to a max_allowed_packet that exceeds the size of the binary log file! Any help would be greatly appreciated. At this point replication is unreliable enough that it doesn't do us any good. Thanks for your help! - Andy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Replication slave gets fatal error 1236 on an almost daily basis.
I have a simple MySQL replication system setup with a single master and a single slave. The slave is running 4.0.16-standard and the master is running 4.0.16-standard-log. On an (almost) daily basis, I get this error on my slave: 031216 9:55:44 Error reading packet from server: log event entry exceeded max_allowed_packet; Increase max_allowed_packet on master (server_errno=1236) 031216 9:55:44 Got fatal error 1236: 'log event entry exceeded max_allowed_packet; Increase max_allowed_packet on master' from master when reading data from binary log 031216 9:55:44 Slave I/O thread exiting, read up to log 'el-bin.001', position 589631188 Note, this does not happen at the same time during the day and it does not happen every day. I know this is not a problem with max_allowed_packet because I have set both the master and slave to a max_allowed_packet that exceeds the size of the binary log file! Any help would be greatly appreciated. At this point replication is unreliable enough that it doesn't do us any good. -- Andy DePue Software Developer Software Services, Inc. (864) 271-8053 x104 -- 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]
Error 1236?
Hello. I'm using replication both master and slave are MySQL 4.0.10. But, When I insert many record( ten thousands of record) at a once, I got follow error message. ### 030219 18:03:20 Error reading packet from server: binlog truncated in the middle of event (server_errno=1236) 030219 18:03:20 Got fatal error 1236: 'binlog truncated in the middle of event' from master when reading data from binary log 030219 18:03:20 Slave I/O thread exiting, read up to log 'test42-bin.003', position 5329913 ### what does this mean? and what shoud I do? somebody help me~ Replication status after error: mysql show slave status \G *** 1. row *** Master_Host: 203.231.xx.xx Master_User: repli Master_Port: 3306 Connect_retry: 10 Master_Log_File: test42-bin.003 Read_Master_Log_Pos: 5329913 Relay_Log_File: wertyu-relay-bin.002 Relay_Log_Pos: 5329973 Relay_Master_Log_File: test42-bin.003 Slave_IO_Running: No Slave_SQL_Running: Yes Replicate_do_db: Replicate_ignore_db: mysql Last_errno: 0 Last_error: Skip_counter: 0 Exec_master_log_pos: 5299624 Relay_log_space: 5329977 1 row in set (0.00 sec) mysql show master status \G *** 1. row *** File: test42-bin.003 Position: 5393075 Binlog_do_db: Binlog_ignore_db: intranet,mysql,repli_test,sfactive,test,traffic,wertyu 1 row in set (0.00 sec) Thank you for advanced answer! ## Heo, Jungsu Mr. SimpleX Internet. http://www.simplexi.com Filter : sql - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail mysql-unsubscribe-##L=##[EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
