Changes between Version 46 and Version 47 of Replication_Issues

Timestamp:

Feb 23, 2012, 8:58:19 AM (14 years ago)

Author:

Serge CHASTEL

Comment:

--

Replication_Issues

@@ -5 +5 @@
 
 = 20120223/08:40: ippdb03 =
-{{{Duplicate entry '350431-P2' for key 1' on query. Default database: 'ipptopsps'}}}. Roy did it.
-{{{}}}
-
+{{{Duplicate entry 'XXXXX-X' for key 1' on query. Default database: 'ipptopsps'}}}. I ran {{{~schastel/dev/many_failures/fix_replication.sh}}} about 200 times without success. I talked to Roy who will replicate ipptopsps somewhere else. I'm dropping it from replication for now.
+I stopped the mysql server on ippdb03, modified /etc/mysql/my.cnf (commented out ipptopsps replication), and restarted the server.
 = 20120222/09:21: ippc19 =
 Replication on ippc19 broke. The 'SHOW SLAVE STATUS\G' command showed the following message: {{{"Slave: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 0"}}}. /var/log/mysql/mysqld.err that replication was broken at log 'mysqld-bin.000639' position 1041257298 (see message {{{120222  8:46:23}}}). I stopped the slave, changed the master coordinates on the slave (with the input found in /var/log/mysql/mysqld.err) and restarted the slave, taht is: