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]