Hi, We currently use in one of our projects 3.23.41 with two-way replication as follows:
|----------| GPW replication |-----------| | MySQL 1 | ------------------------------------------> | MySQL 2 | |GPW Master| |GPW Slave | |GPW1 Slave| GPW1 replication |GPW1 Master| |----------| <------------------------------------------ |-----------| GPW and GPW1 are databases with the same structure. my.cnf from MySQL 1: [mysqld] master-host=[ip of 2nd MySQL] master-user=xxx master-password=xxxx master-connect-retry=10 replicate-do-db=GPW1 replicate-ignore-table=GPW1.tmp replicate-ignore-table=GPW1.tmp1 replicate-ignore-table=GPW1.tmp2 replicate-ignore-table=GPW1.a replicate-ignore-table=GPW1.b replicate-ignore-table=GPW1.c replicate-ignore-table=GPW1.d replicate-ignore-table=GPW1.e server-id=3 log-bin my.cnf of 2nd MySQL: [mysqld] master-host=[ip of 1st MySQL] master-user=xxxx master-password=xxxxx master-connect-retry=10 replicate-do-db=GPW replicate-ignore-table=GPW.tmp1 replicate-ignore-table=GPW.tmp replicate-ignore-table=GPW.tmp2 replicate-ignore-table=GPW.a replicate-ignore-table=GPW.c replicate-ignore-table=GPW.b replicate-ignore-table=GPW.d replicate-ignore-table=GPW.e server-id=4 log-bin We are frequently receiving errors in binary log which effect in replication failure: 011017 0:48:50 Slave: did not get the expected error running query from master - expected: 'Got timeout reading communication packets'(1159), got 'no error'(0) 011017 0:48:50 Slave: error running query 'drop table GPW.d' 011017 0:48:50 Error running query, slave aborted. Fix the problem, and re-start the slave thread with "mysqladmin start-slave". We stopped at log 'testdb1-bin.020' position 570891011 011017 0:48:50 Slave thread exiting, replication stopped in log 'testdb1-bin.020' at position 570891011 What is the reason of "did not get the expected error running query from master - expected: 'Got timeout reading communication packets'(1159), got 'no error'(0)" entry? GPW.d is a temporary table made probably by MySQL from query like: "Select d.foo as abc, e.foo2 as def from bar d, bar2 e;" Maillist archives says that the problem with temporary tables in replication was fixed in 3.23.37 Besides we put "replicate-ignore-table=GPW.d" entry in my.cnf for both databases. :: Bartek Papierski kierownik oddzialu mailto:[EMAIL PROTECTED] tel. +48 42 631 11 66 mobile +48 609 665 091 :: K2 internet sa o/Lodz http://www.k2.pl 90-418 lodz, al. kosciuszki 1 tel. +48 42 631 11 66 fax +48 42 631 11 66 --------------------------------------------------------------------- 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 <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php