In some email I received from "Ingo Brand" <[EMAIL PROTECTED]> on Fri, 6 Jun 2003 13:24:09 +0200, wrote:
> hi, > > we have some replication-problems using dbmail 1.1 and mysql 4.0.13. > we updated the database today because we want to use the nice query-cache in > mysql-4.0. > we have to datebase-servers with mysql-master-slave-replication. > everything is ok with it except that the synchronisation gets lost very > often since we updatet the db: > > ERROR: 1062 Duplicate entry '17603' for key 1 > 030606 13:11:37 Slave: error 'Duplicate entry '17603' for key 1' on query > 'INSERT INTO messageblks(messageblk,blocksize,message_idnr) VALUES etc.... That has to do with the unique ids :) Or there's something wrong with the binary log files on one of the servers . Take a look at http://www.mysql.com/doc/en/Replication_Problems.html. And still at the end of the day you have to fix it manually. I'd suggest re-init the slave, or continue from specific position etc etc.. the url will tell you. Anyway I know the feeling I was running a multimaster kinda replication with dbmail after a month and more without a fault something happened to the mysql daemon and it didnt sync properly, after this problem i stopped using mysql replication and mysql in general. Now I'm using Postfix+Dbmail+PgSQL+Pg Replicator+scheme with different increment factors for each server. (Basically I dont replicate sequences but each database generates different ones: <sql> CREATE SEQUENCE NAME START %server_id INCREMENT %servers_sum; </sql> ) I did some smashing tests for about few days, start restart crash burn :) it worked, so I moved to it, also the good thing is that Pg Replicator has algorithms to resolve collision and other types of conflicts, which makes it more attractive option. > it is always the same insert-command which causes the mysql-slave to stop > replication. has anyone a solution for it? > > btw.: all other replication-things are working ok... > > since the upgrade we had about 180000 updates and 30000 inserts which were > replicated correctly... only dbmail makes problems... cheers, -lou
