IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 55 and Version 56 of Replication_Issues


Ignore:
Timestamp:
May 30, 2012, 10:25:44 AM (14 years ago)
Author:
Serge CHASTEL
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Replication_Issues

    v55 v56  
    3131{{{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.
    3232I stopped the mysql server on ippdb03, modified /etc/mysql/my.cnf (commented out ipptopsps replication), and restarted the server.
    33 = 20120222/09:21: ippc19 =
     33== 20120222/09:21: ippc19 ==
    3434Replication 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:
    3535{{{